Device, method, and graphical user interface for accessing an application in a locked device

ABSTRACT

A device with a touch sensitive display and a plurality of applications, including a camera application, while the device is in a locked, passcode-protected state: displays a lock screen interface, the lock screen interface including a camera access indicia; detects a gesture; in response to a determination that the gesture starts on the camera access indicia: ceases to display the lock screen interface; starts a restricted session for the camera application; displays an interface for the camera application, without displaying a passcode entry interface; and maintains the device in the locked, passcode-protected state for the applications other than the camera application; and in response to a determination that the gesture starts at a location other than the camera access indicia: displays a passcode entry interface, wherein in response to ently of a correct passcode in the passcode entry interface, the device enters an unlocked state.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 61/589,239, filed Jan. 20, 2012, entitled “Device, Method, andGraphical User Interface for Accessing a Camera Application While theDevice is Locked”; and U.S. Provisional Application Ser. No. 61/745,189,filed Dec. 21, 2012, entitled “Device, Method, and Graphical UserInterface for Accessing an Application in a Locked Device,” which areincorporated by reference herein in their entireties.

This application is related to U.S. application Ser. No. 13/243,045,filed Sep. 23, 2011, entitled “Device, Method, and Graphical UserInterface for Accessing an Application in a Locked Device,” which isincorporated by reference herein in its entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that enable access to an application while thedevice is locked.

BACKGROUND

The use of portable devices with touch-sensitive surfaces as inputdevices has increased significantly in recent years. Such portabledevices have greatly increased the number of applications, or “apps,”for various situations. For example, image and video camera applicationsopen up content generation opportunities for users, such as takingpictures or recording videos. A notes application allows a user to reador write notes on the fly. Time may be critical in such contentgeneration opportunities. For example, a user may have only a briefmoment to capture an image or a video of an event as it is happening.

But existing methods for accessing applications are slow and a hindranceto quick usage, particularly when the device is in a locked,passcode-protected state. Accessing an application on a device,including accessing different modes of the application, while the deviceis locked requires multiple steps, which prevent immediate or quickaccess to the application in situations when immediate or quick accessis beneficial or desired.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for accessing an application while thedevice is locked. Such methods and interfaces may complement or replaceconventional methods for accessing an application while the device islocked. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions may include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions may be included in anon-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a portablemultifunction device with a touch-sensitive display and a plurality ofapplications, including a camera application. The method includes: whilethe device is in a locked, passcode-protected state: displaying a lockscreen interface on the touch-sensitive display, the lock screeninterface including a camera access indicia; detecting a gesture on thetouch-sensitive display; in response to a determination that the gesturestarts on the camera access indicia: ceasing to display the lock screeninterface, starting a restricted session for the camera application,displaying an interface for the camera application, without displaying apasscode entry interface, and maintaining the device in the locked,passcode-protected state for applications in the device other than thecamera application; and in response to a determination that the gesturestarts at a location on the touch-sensitive display other than thecamera access indicia, displaying a passcode entry interface, wherein inresponse to entry of a correct passcode in the passcode entry interface,the passcode entry interface ceases to be displayed and the deviceenters an unlocked state with access to the plurality of applications.

In accordance with some embodiments, a method is performed at a portablemultifunction device with a touch-sensitive display and a plurality ofapplications, including a camera application. The method includes: whilethe device is in a locked, passcode-protected state: displaying a lockscreen interface on the touch-sensitive display, the lock screeninterface including a camera access indicia and an unlock indicia; inresponse to detecting a gesture that starts and ends on the cameraaccess indicia: ceasing to display the lock screen interface, starting arestricted session for the camera application, displaying an interfacefor the camera application, without displaying a passcode entryinterface, and maintaining the device in the locked, passcode-protectedstate for applications in the device other than the camera application;and in response to detecting a gesture that starts at a location on thetouch-sensitive display associated with the unlock indicia, displaying apasscode entry interface, wherein in response to entry of a correctpasscode in the passcode entry interface, the passcode entry interfaceceases to be displayed and the device enters an unlocked state withaccess to the plurality of applications.

In accordance with some embodiments, a method is performed at a portablemultifunction device with a touch-sensitive display and a plurality ofapplications, including a camera application. The method includes: whilethe device is in a locked, passcode-protected state: displaying a lockscreen interface on the touch-sensitive display, the lock screeninterface including an unlock indicia and a camera access indicia; inresponse to detecting a gesture that ends on the camera access indicia:ceasing to display the lock screen interface, starting a restrictedsession for the camera application, displaying an interface for thecamera application, without displaying a passcode entry interface, andmaintaining the device in the locked, passcode-protected state forapplications in the device other than the camera application; and inresponse to detecting a gesture that ends at a location on thetouch-sensitive display associated with the unlock indicia, displaying apasscode entry interface, wherein in response to entry of a correctpasscode in the passcode entry interface, the passcode entry interfaceceases to be displayed and the device enters an unlocked state withaccess to the plurality of applications.

In accordance with some embodiments, a method is performed at a portablemultifunction device with a touch-sensitive display and a plurality ofapplications, including a camera application. The method includes: whilethe device is in a locked, passcode-protected state: displaying a lockscreen interface on the touch-sensitive display, the lock screeninterface including a camera access indicia; detecting a gesture on thetouch-sensitive display; in response to a determination that the gesturestarts on the camera access indicia and is of a first type, partiallyrevealing an interface for the camera application; in response to adetermination that the gesture starts on the camera access indicia andis of a second type different from the first type, ceasing to displaythe lock screen interface, starting a restricted session for the cameraapplication, displaying an interface for the camera application, withoutdisplaying a passcode entry interface, and maintaining the device in thelocked, passcode-protected state for applications in the device otherthan the camera application; and in response to a determination that thegesture starts at a location on the touch-sensitive display other thanthe camera access indicia, displaying a passcode entry interface,wherein in response to entry of a correct passcode in the passcode entryinterface, the passcode entry interface ceases to be displayed and thedevice enters an unlocked state with access to the plurality ofapplications.

In accordance with some embodiments, a portable multifunction deviceincludes a touch-sensitive display, one or more processors, memory, aplurality of applications, including a camera applications, and one ormore programs; the one or more programs are stored in the memory andconfigured to be executed by the one or more processors and the one ormore programs include instructions for performing the operations of anyof the methods described above. In accordance with some embodiments, agraphical user interface on a portable multifunction device with atouch-sensitive display, a memory, a plurality of applications,including a camera application, and one or more processors to executeone or more programs stored in the memory includes one or more of theelements displayed in any of the methods described above, which areupdated in response to inputs, as described in any of the methods above.In accordance with some embodiments, a computer readable storage mediumhas stored therein instructions which when executed by a portablemultifunction device with a touch-sensitive display and a plurality ofapplications including a camera application, cause the device to performthe operations of any of the methods described above. In accordance withsome embodiments, a portable multifunction device includes: atouch-sensitive display; a plurality of applications, including a cameraapplication; and means for performing the operations of any of themethods described above. In accordance with some embodiments, aninformation processing apparatus, for use in a portable multifunctiondevice with a touch-sensitive display and a plurality of applications,including a camera application, includes means for performing theoperations of any of the methods described above.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a camera access indicia, and receivegestures; a plurality of applications, including a camera application;and a processing unit coupled to the touch-sensitive display unit andthe plurality of applications. The processing unit is configured to:while the device is in the locked, passcode-protected state: detect agesture on the touch-sensitive display unit; in response to adetermination that the gesture starts on the camera access indicia:cease to display the lock screen interface, start a restricted sessionfor the camera application, enable display of an interface for thecamera application, without displaying a passcode entry interface, andmaintain the device in the locked, passcode-protected state forapplications in the device other than the camera application; and inresponse to a determination that the gesture starts at a location on thetouch-sensitive display unit other than the camera access indicia,enable display of a passcode entry interface, wherein in response toentry of a correct passcode in the passcode entry interface, thepasscode entry interface ceases to be displayed and the device enters anunlocked state with access to the plurality of applications.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a camera access indicia and an unlockindicia, and receive gestures; a plurality of applications, including acamera application; and a processing unit coupled to the touch-sensitivedisplay unit and the plurality of applications. The processing unit isconfigured to: while the device is in the locked, passcode-protectedstate: in response to detecting a gesture that starts and ends on thecamera access indicia, cease to display the lock screen interface, starta restricted session for the camera application, enable display of aninterface for the camera application, without displaying a passcodeentry interface, and maintain the device in the locked,passcode-protected state for applications in the device other than thecamera application; and in response to detecting a gesture that startsat a location on the touch-sensitive display unit associated with theunlock indicia, display a passcode entry interface, wherein in responseto entry of a correct passcode in the passcode entry interface, thepasscode entry interface ceases to be displayed and the device enters anunlocked state with access to the plurality of applications.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a camera access indicia and an unlockindicia, and receive gestures; a plurality of applications, including acamera application; and a processing unit coupled to the touch-sensitivedisplay unit and the plurality of applications. The processing unit isconfigured to: while the device is in the locked, passcode-protectedstate: in response to detecting a gesture that ends on the camera accessindicia: cease to display the lock screen interface, start a restrictedsession for the camera application, enable display of an interface forthe camera application, without displaying a passcode entry interface,and maintain the device in the locked, passcode-protected state forapplications in the device other than the camera application; and inresponse to detecting a gesture that ends at a location on thetouch-sensitive display unit associated with the unlock indicia, displaya passcode entry interface, wherein in response to entry of a correctpasscode in the passcode entry interface, the passcode entry interfaceceases to be displayed and the device enters an unlocked state withaccess to the plurality of applications.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a camera access indicia, and receivegestures; a plurality of applications, including a camera application;and a processing unit coupled to the touch-sensitive display unit andthe plurality of applications. The processing unit is configured to:while the device is in the locked, passcode-protected state: detect agesture on the touch-sensitive display unit; in response to adetermination that the gesture starts on the camera access indicia andis of a first type, partially reveal an interface for the cameraapplication; in response to a determination that the gesture starts onthe camera access indicia and is of a second type different from thefirst type, cease to display the lock screen interface, start arestricted session for the camera application, enable display of aninterface for the camera application, without displaying a passcodeentry interface and maintain the device in the locked,passcode-protected state for applications in the device other than thecamera application; and in response to a determination that the gesturestarts at a location on the touch-sensitive display unit other than thecamera access indicia, enable display of a passcode entry interface,wherein in response to entry of a correct passcode in the passcode entryinterface, the passcode entry interface ceases to be displayed and thedevice enters an unlocked state with access to the plurality ofapplications.

In accordance with some embodiments, a method is performed at a portabledevice with a touch-sensitive display and a plurality of applications,including a first application. The method includes: while the device isin a locked, passcode-protected state: displaying a lock screeninterface on the touch-sensitive display, the lock screen interfaceincluding a first application access indicia; detecting a gesture on thetouch-sensitive display; in response to a determination that the gesturestarts on the first application access indicia and is a first type ofgesture: ceasing to display the lock screen interface; starting arestricted session for the first application in a first mode of thefirst application; displaying an interface for the first application inthe first mode, without displaying a passcode entry interface; andmaintaining the device in the locked, passcode-protected state forapplications in the device other than the first application; and inresponse to a determination that the gesture starts on the firstapplication access indicia and is a second type of gesture, distinctfrom the first type of gesture: ceasing to display the lock screeninterface; starting a restricted session for the first application in asecond mode of the first application, distinct from the first mode ofthe first application; displaying an interface for the first applicationin the second mode, without displaying a passcode entry interface; andmaintaining the device in the locked, passcode-protected state forapplications in the device other than the first application.

In accordance with some embodiments, a method is performed at a portabledevice with a touch-sensitive display and a plurality of applications,including a first application. The method includes: while the device isin a locked, passcode-protected state: displaying a lock screeninterface on the touch-sensitive display, the lock screen interfaceincluding a first access indicia for a first mode in a first applicationand a second access indicia, distinct from the first access indicia fora second mode in the first application; detecting a gesture on thetouch-sensitive display; in response to a determination that the gesturestarts on the first access indicia and is a first type of gesture:ceasing to display the lock screen interface; starting a restrictedsession for the first application in a first mode of the firstapplication; displaying an interface for the first application in thefirst mode, without displaying a passcode entry interface; andmaintaining the device in the locked, passcode-protected state forapplications in the device other than the first application; and inresponse to a determination that the gesture starts on the second accessindicia and is a second type of gesture: ceasing to display the lockscreen interface; starting a restricted session for the firstapplication in a second mode of the first application, distinct from thefirst mode of the first application; displaying an interface for thefirst application in the second mode, without displaying a passcodeentry interface; and maintaining the device in the locked,passcode-protected state for applications in the device other than thefirst application.

In accordance with some embodiments, a portable device includes atouch-sensitive display, one or more processors, memory, a plurality ofapplications, including a first application, and one or more programs;the one or more programs are stored in the memory and configured to beexecuted by the one or more processors and the one or more programsinclude instructions for performing the operations of any of the methodsdescribed above. In accordance with some embodiments, a graphical userinterface on a portable device with a touch-sensitive display, a memory,a plurality of applications, including a first application, and one ormore processors to execute one or more programs stored in the memoryincludes one or more of the elements displayed in any of the methodsdescribed above, which are updated in response to inputs, as describedin any of the methods above. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by a portable device with a touch-sensitive display and aplurality of applications, including a first application, cause thedevice to perform the operations of any of the methods described above.In accordance with some embodiments, a portable device includes: atouch-sensitive display, a plurality of applications, including a firstapplication; and means for performing the operations of any of themethods described above. In accordance with some embodiments, aninformation processing apparatus, for use in a portable device with atouch-sensitive display and a plurality of applications, including afirst application, includes means for performing the operations of anyof the methods described above.

In accordance with some embodiments, a portable device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a first application access indicia, andreceive gestures; a plurality of applications, including a firstapplication; and a processing unit coupled to the touch-sensitivedisplay unit and the plurality of applications. The processing unit isconfigured to, while the device is in a locked, passcode-protectedstate: detect a gesture on the touch-sensitive display unit; in responseto a determination that the gesture starts on the first applicationaccess indicia and is a first type of gesture: cease display of the lockscreen interface, start a restricted session for the first applicationin a first mode of the first application, enable display of an interfacefor the first application in the first mode, without displaying apasscode entry interface, and maintain the device in the locked,passcode-protected state for applications in the device other than thefirst application; and in response to a determination that the gesturestarts on the first application access indicia and is a second type ofgesture, distinct from the first type of gesture: cease display of thelock screen interface, start a restricted session for the firstapplication in a second mode of the first application, distinct from thefirst mode of the first application, enable display of an interface forthe first application in the second mode, without displaying a passcodeentry interface, and maintain the device in the locked,passcode-protected state for applications in the device other than thefirst application.

In accordance with some embodiments, a portable device includes atouch-sensitive display unit configured to display, while the device isin a locked, passcode-protected state, a lock screen interface, the lockscreen interface including a first access indicia for a first mode in afirst application and a second access indicia, distinct from the firstaccess indicia, for a second mode in the first application, and receivegestures; a plurality of applications, including a first application;and a processing unit coupled to the touch-sensitive display unit andthe plurality of applications. The processing unit is configured to,while the device is in a locked, passcode-protected state: detect agesture on the touch-sensitive display; in response to a determinationthat the gesture starts on the first access indicia and is a first typeof gesture: cease to display the lock screen interface, start arestricted session for the first application in a. first mode of thefirst application, enable display of an interface for the firstapplication in the first mode, without displaying a passcode entryinterface, and maintain the device in the locked, passcode-protectedstate for applications in the device other than the first application;and in response to a determination that the gesture starts on the secondaccess indicia and is a second type of gesture: cease to display thelock screen interface, start a restricted session for the firstapplication in a second mode of the first application, distinct from thefirst mode of the first application, enable display of an interface forthe first application in the second mode, without displaying a passcodeentry interface, and maintain the device in the locked,passcode-protected state for applications in the device other than thefirst application.

Thus, portable multifunction devices with touch-sensitive displays areprovided with faster, more efficient methods and interfaces foraccessing an application in a locked device, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor accessing an application in a locked device.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4 illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIGS. 5A-5TTT illustrate exemplary user interfaces for accessing acamera application in a. locked device in accordance with someembodiments.

FIGS. 6A-6B are flow diagrams illustrating a method of accessing acamera application in a locked device in accordance with someembodiments.

FIG. 7 is a flow diagram illustrating a method of accessing a cameraapplication in a locked device in accordance with some embodiments.

FIG. 8 is a flow diagram illustrating a method of accessing a cameraapplication in a locked device in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method of accessing a cameraapplication in a locked device in accordance with some embodiments.

FIGS. 10A-10C are flow diagrams illustrating a method of accessingdifferent modes of an application in a locked device in accordance withsome embodiments.

FIGS. 11A-11C are flow diagrams illustrating a method of accessingdifferent modes of an application in a locked device in accordance withsome embodiments.

FIG. 12 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Typically, accessing an application in a locked device takes severalsteps and corresponding user inputs. For example, the steps may includeunlocking the device with a passcode, navigating to an iconcorresponding to the application, and activating the icon. While havingto unlock the device with a passcode first provides device security,there are times when having to unlock the device first to access anapplication is a hindrance, such as when trying to capture fleetingmoments in a still image or video with a camera application. Theembodiments described below enable a user to access a first application(e.g., a camera application), including different modes of the firstapplication, without the user entering the passcode; the passcodeprotection is bypassed. In some embodiments, while the device is locked,an interface with a camera access indicia is displayed. In someembodiments, when a gesture starts on the camera access indicia, acamera application is started in a restricted session, whereas when thesame gesture starts away the camera access indicia, a passcode entryinterface is displayed. In some embodiments, when a gesture ends on thecamera access indicia, a camera application is started in a restrictedsession, whereas when the gesture ends on an unlock indicia, a passcodeentry interface is displayed. The gesture on the camera access indiciaprovides for rapid access to the camera (e.g., by bypassing passcodeinput) and also maintains device security in view of the bypassing ofthe passcode input (e.g., by placing restrictions on use of the cameraapplication and maintaining the device in a locked state with respect toother applications). Quick camera application access when the device isin a locked, passcode-protected state is particularly useful forportable devices (e.g., smart phones, tablet computers, laptopcomputers), but can also be used with other devices (e.g., desktopcomputers).

In some other embodiments, while the device is locked, an interface withan application access indicia is displayed. When a gesture starts on theapplication access indicia, depending on the type of gesture, anapplication associated with the application access indicia is started ina restricted session in one of multiple modes. In some otherembodiments, while the device is locked, an interface with both a firstaccess indicia and a second access indicia is displayed. The first andsecond access indicia are associated with an application. When a gesturestarts on the first access indicia, the application is started in arestricted session in a first mode of the application. When a gesturestarts on the second access indicia, the application is started in arestricted session in a second mode of the application. The gesture onthe access indicia provides for rapid access to different modes of anapplication (e.g., by bypassing passcode input) and also maintainsdevice security in view of the bypassing of the passcode input (e.g., byplacing restrictions on use of the started application and maintainingthe device in a locked state with respect to other applications).

Below, FIGS. 1A-1B, 2, 3 provide a description of exemplary devices.FIGS. 4 and 5A-5TTT illustrate exemplary user interfaces for accessingan application in a locked device. FIGS. 6A-6B, 7-9, 10A-10C, and11A-11C are flow diagrams illustrating methods of accessing anapplication in a locked device. The user interfaces in FIGS. 5A-5TTT areused to illustrate the processes in FIGS. 6A-6B, 7 8, 9, 10A-10C, and11A-11C.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to he limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 100 may includememory 102 (which may include one or more computer readable storagemediums), memory controller 122, one or more processing units (CPU's)120, peripherals interface 118, RF circuitry 108, audio circuitry 110,speaker 111, microphone 113, input/output (I/O) subsystem 106, otherinput or control devices 116, and external port 124. Device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 1A may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, the one or moreprocessors 120 include an image signal processor and a dual-core ormulti-core processor.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may he implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), high-speed uplink packet access (HSUPA),wideband code division multiple access (W-CDMA), code division multipleaccess (CDMA), time division multiple access (TDMA), Bluetooth, WirelessFidelity (Wi-Fi) (e.g., IEEE 802.11a., IEEE 802.11b, IEEE 802.11g and/orIEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocolfor e-mail (e.g., Internet message access protocol (MAP) and/or postoffice protocol (POP)), instant messaging (e.g., extensible messagingand presence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118, I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. In some embodiments, the proximity sensor turnsoff and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices 1and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components. Further, in some embodiments, memory 102 storescamera roll 159 and digital image pipeline 161.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which may be made up of a        video player module and a music player module;    -   notes module 153;    -   map module 154;    -   online video module 155;    -   voice/audio recorder module 163; and/or    -   notifications module 165.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108. audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with FT circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RE circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, UPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, digital image pipeline 161 (which converts raw datafrom the optical sensor into a final image or video), and imagemanagement module 144, camera module 143 includes executableinstructions to capture still images or video (including a video stream)and store them into memory 102 (e.g., in camera roll 159), modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102 (e.g., from camera roll 159).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images, including still and/or video images stored in camera roll159.

In conjunction with RE circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 10$, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars e g calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 mayhe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, and microphone 113, voice/audio recorder module 163 includesexecutable instructions that allow the user to record audio (e.g.,voice) in one or more file formats, such as MP3 or AAC files, andexecutable instructions to present or otherwise play back the recordedaudio files.

In conjunction with touch screen 112, display system controller 156,contact module 130, and graphics module 132, notifications module 165includes executable instructions that display notifications or alerts,such as incoming messages or phone calls, calendar event reminders,application events, and so on, on touch screen 112.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may he combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIGS. 1A) or 370 (FIG. 3) includes event sorter 170(e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In vet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180, Typically, a respective application view 191 includes a pluralityof event recognizers 180. in other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI. updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In sonic embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (U1) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 202 (not drawn to scale in the figure) or oneor more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. In some embodiments,processing unit(s) 310 include an image signal processor and a dual-coreor multi-core processor. Communication buses 320 may include circuitry(sometimes called a chipset) that interconnects and controlscommunications between system components. Device 300 includesinput/output (I/O) interface 330 comprising display 340, which istypically a touch screen display. I/O interface 330 also may include akeyboard and/or mouse (or other pointing device) 350 and touchpad 355.Device 300 also includes optical sensor(s) 164 and optical sensor(s)controller 158. Memory 370 includes high-speed random access memory,such as DRAM, SRAM, DDR RAM or other random access solid state memorydevices; and may include non-volatile memory, such as one or moremagnetic disk storage devices, optical disk storage devices, flashmemory devices, or other non-volatile solid state storage devices.Memory 370 may optionally include one or more storage devices remotelylocated from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1), or a subset thereof. Furthermore,memory 370 may store additional programs, modules, and data structuresnot present in memory 102 of portable multifunction device 100. Forexample, memory 370 of device 300 may store drawing module 380,presentation module 382, word processing module 384, website creationmodule 386, disk authoring module 388, and/or spreadsheet module 390,while memory 102 of portable multifunction device 100 (FIG. 1) may notstore these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that may be implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Phone 138, which may include an indicator 414 of the number            of missed calls or voicemail messages;        -   E-mail client 140, which may include an indicator 410 of the            number of unread e-mails;        -   Browser 147; and        -   Video and music player 152, also referred to as iPod            (trademark of Apple Inc.) module 152; and    -   Icons for other applications, such as:        -   IM 141;        -   image management 144;        -   Camera 143;        -   Weather 149-1;        -   Stocks 149-2;        -   Workout support 142;        -   Calendar 148;        -   Alarm clock 149-4;        -   Map 154;        -   Notes 153;        -   Settings 412, which provides access to settings for device            100 and its various applications 136; and        -   Online video module 155, also referred to as YouTube            (trademark of Google Inc.) module 155.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., stylus input).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronic devicewith a display and a touch-sensitive surface, such as device 300 orportable multifunction device 100.

FIGS. 5A-5TTT illustrate exemplary user interfaces for accessing anapplication in a locked device in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 6A-6B, 7, 8, 9,10A-10C, 11A-11C.

FIG. 5A illustrates locked device interface 5000-A displayed on touchscreen 112 of device 100. Locked device interface 5000-A may bedisplayed when a physical button (e.g., push button 206, home or menubutton 204) on device 100 is activated by a user while device 100 is ina locked state. Locked device interface 5000-A may include a messageinforming the user that the device is locked, as well as otherinformation (e.g., current time and date).

Device 100 may be in a locked, passcode-protected state or in a locked,not-passcode-protected state. When device 100 is in the locked,passcode-protected state, a passcode is required to unlock device 100.When device 100 is in the locked, not-passcode-protected state, apasscode is not required to unlock device 100.

Locked device interface 5000-A includes camera access indicia 5006. Insome embodiments, camera access indicia includes icon 5008 indicating acamera application and “grabbing handle” icon(s) 5010 indicating thatcamera access indicia 5006 may be interacted with by the user (e.g.,“grabbed” in a dragging or sliding gesture). In some embodiments, cameraaccess indicia 5006 is displayed in a predefined region (e.g., region5012) of locked device interface 5000-A.

A gesture may be detected on touch screen 112 as starting at somelocation in region 5012 on touch screen 112. In FIG. 5A, the gesture maystart on camera access indicia 5006 or at a location in region 5012other than camera access indicia 5006, and move in some direction. Forexample, gesture 5014 starts on camera access indicia 5006 and moveswith movement 5016. Gesture 5018 starts at a location in region 5012other than on camera access indicia 5006 and moves with movement 5020.

In response to the detection of gesture 5018 and a determination thatgesture 5018 starts at a location in region 5012 other than cameraaccess indicia 5006, region 5012 expands in accordance with thedirection of movement 5020, as shown in FIG. 5B, and transitions intopasscode entry user interface 5022 (FIG. 5C) if device 100 was in alocked, passcode-protected state. When movement 5020 is complete (e.g.,reaches the top of touch screen 112), locked device interface 5000-Aceases to be displayed, and passcode entry user interface 5022 isdisplayed is displayed on touch screen 112 (as shown in FIG. 5C). Ifdevice 100 was in a locked, not-passcode-protected state, device 100 isunlocked when movement 5020 is complete.

In response to the detection of gesture 5014 and a determination thatgesture 5014 starts on camera access indicia 5006, if device 100 was ina locked, passcode-protected state, region 5012 expands (e.g., in ananimation) in accordance with the direction of movement 5016, as shownin FIG. 5B, and transitions into camera interface 5026 (FIG. 5D) ofcamera application 143 in a restricted session. When movement 5016 iscomplete (e.g., reaches the top of touch screen 112) and gesture 5014 isreleased, locked device interface 5000-A ceases to be displayed, andcamera interface 5026 is displayed on touch screen 112. If device 100 isin a locked, passcode-protected state when gesture 5014 is released, thelocked, passcode-protected state is maintained for applications ondevice 100 other than camera application 143, while camera application143 is in a restricted session. Thus, camera application 143 is startedin a restricted session in response to the detection of gesture 5014.

In some embodiments, while device 100 is in the locked,passcode-protected state, in response to the detection, on touch screen112, of gestures not similar to gesture 5018 or 5014, device 100 isprevented from performing a predefined set of actions in response to thedetection of those contacts. The predefined set of actions include, forexample, displaying passcode entry user interface 5022 and unlockingdevice 100.

If device 100 was in a locked, not-passcode-protected state, in responseto the detection of gesture 5014 and a determination that gesture 5014starts on camera access indicia 5006, region 5012 expands (e.g., in ananimation) in accordance with the direction of movement 5016, as shownin FIG. 5B, and transitions into camera interface 5026 (FIG. 5D) ofcamera application 143 in an unrestricted session. When movement 5016 iscomplete (e.g., reaches the top of touch screen 112) and gesture 5014 isreleased, locked device interface 5000-A ceases to be displayed, camerainterface 5026 is displayed on touch screen 112, and device 100 isunlocked (i.e., camera application 143 is fully functional, and otherapplications on device 100 are accessible and fully functional).

FIG. 5D shows camera interface 5026 of camera application 143 displayedon touch screen 112. Camera interface 5026 includes viewfinder area5028, shutter icon 5030, still-image/video mode toggle switch 5032, andcamera roll icon 5034. A live image preview 5036 may be displayed inviewfinder area 5028. In response to the detection of a gesture (e.g.,tap gesture 5038) on shutter icon 5030, a still image is captured andsaved into camera roll 159, and a thumbnail preview of the just-capturedimage is displayed in camera roll icon 5034. In response to activationof toggle switch 5032, camera application 143 switches between stillimage capture mode and video capture mode (while remaining in therestricted session, if camera application 143 was started in arestricted session).

In response to the detection of a gesture (e,g., tap gesture 5040) oncamera roll icon 5034, camera roll image viewer interface 5042 of cameraapplication 143 is displayed along with the image(s) 5044 in camera roll159 that satisfy one or more predefined presentation criteria, as shownin FIG. 5E. Camera roll image viewer interface 5042 includes controls5046 for, for example, browsing through images and videos in camera roll159 that satisfy the presentation criteria, starting a slideshow of saidimages, or deleting a currently displayed image. Camera roll imageviewer interface 5042 also includes camera interface icon 5048 andnavigation icon 5050. In response to the detection of a gesture (e.g.,tap gesture 5052) on camera interface icon 5048, display of camera rollimage viewer interface 5042 is replaced by display of camera interface5026 (FIG. 5D), and camera application 143 remains in the restrictedsession if camera application 143 was started in a restricted session.In response to the detection of a gesture (e.g., tap gesture 5054) onnavigation icon 5050, display of camera roll image viewer interface 5042is replaced by display of camera roll thumbnails interface 5056 ofcamera application 143, as shown in FIG. 5F.

In FIG. 5F, camera roll thumbnails interface 5056 includes zero or morethumbnails 5058 of images (i.e., still images and/or videos) in cameraroll 159 that are captured by camera application 143 and which satisfythe one or more predefined presentation criteria. In response toselection of a thumbnail 5058 (e.g., by performing a gesture on therespective thumbnail 5058 in thumbnails interface 5056), camera rollimage viewer interface 5042 is displayed, as in FIG. 5E, and the imagecorresponding to the selected thumbnail 5058 is displayed in camera rollimage viewer interface 5042. Also included in thumbnails interface 5056are camera interface icon 5048 and type selection icons 5060. Inresponse to the detection of a gesture (e.g., tap gesture 5062) oncamera interface icon 5048, camera interface 5026 is displayed, as inFIG. 50, and camera application 143 remains in the restricted session.In response to selection of a type selection icon (“all,” “photos,”“videos”), thumbnails 5058 displayed in thumbnails interface 5056 may beswitched amongst both photos (still images) and videos, just photos, orjust videos.

The images and videos (e.g., image 5044) and thumbnails 5058 that aredisplayed or presented in image viewer interface 5042 and thumbnailsinterface 5056, respectively, satisfy one or more predefinedpresentation criteria. In some embodiments, the presentation criterionis that an image or video (or for a thumbnail, the image or videocorresponding to the thumbnail), in order to be presented in imageviewer interface 5042 and thumbnails interface 5056 while in therestricted session, must be generated (captured) by camera application143 while in a restricted session (and, in some embodiments, while inthe current restricted session). In other words, only images and videoscaptured in camera application 143 in a restricted session andcorresponding thumbnails are presented in image viewer interface 5042and thumbnails interface 5056, respectively, while in the restrictedsession, and images and videos generated in camera application 143 whiledevice 100 is unlocked and corresponding thumbnails are not presented inimage viewer interface 5042 and thumbnails interface 5056, and thus areinaccessible for viewing while in a restricted session. Images capturedin any restricted session, and corresponding thumbnails, are accessiblefor viewing in camera application 143 while device 100 is unlocked. Thepresentation criteria are further described in U.S. application Ser. No.13/243,045, filed Sep. 23, 2011, entitled “Device, Method, and GraphicalUser Interface for Accessing an Application in a Locked Device,” whichis incorporated herein by reference in its entirety.

Camera application 143 may be deactivated, and the restricted sessionended, by activating, for example, push button 206 or homes/menu button204 while camera interface 5026, camera roll image viewer interface5042, or thumbnails interface 5056 is displayed on touch screen 112while camera application 143 is active in the restricted session. Inresponse to activation of push button 206 or home/menu button 204, therestricted session is ended and camera interface 5026. camera roll imageviewer interface 5042, and thumbnails interface 5056 cease to bedisplayed.

In some embodiments, while camera interface 5026 is displayed, inresponse to the detection of a swipe gesture in one direction (e.g.,substantially horizontal and rightward, as in gesture 5037 (FIG. 5D)) ontouch screen 112, display of camera interface 5026 is replaced bydisplay of camera roll image viewer interface 5042. While camera rollimage viewer interface 5042 or camera roll thumbnails interface 5056 isdisplayed, in response to the detection of a swipe gesture in theopposite direction (e.g., substantially horizontal and leftward, as ingesture 5039 (FIG. 5E) or gesture 5041 (FIG. 5F)) on touch screen 112,display of camera roll image viewer interface 5042 is replaced bydisplay of camera interface 5026.

It should be appreciated that while FIGS. 5D thru 5F are described abovewith respect to a still image capture mode for camera application 143,the description of these figures apply analogously to a video capturemode for camera application 143.

In some embodiments, when gesture 5014 is detected on camera accessindicia 5006, one or more hardware components related to the operationof camera application 143 are initialized. For example, as gesture 5014moves with movement 5016, optical sensor(s) 164 and optical sensor(s)controller 158 are initialized. In some embodiments, one or moresoftware and memory components related to the operation of cameraapplication 143 are also initialized or pre-loaded when gesture 5014 isdetected on camera access indicia 5006. For example, as gesture 5014moves with movement 5016, camera roll 159 and digital image pipeline 161may be pre-loaded. Further details and examples of the initialization orpre-loading of hardware and software components related to the operationof camera application 143 are described in U.S. application Ser. No.13/243,045, filed Sep. 23, 2011, entitled “Device, Method, and GraphicalUser Interface for Accessing an Application in a Locked Device,” whichis incorporated herein by reference in its entirety.

FIG. 5G illustrates locked device interface 5000-B displayed on touchscreen 112 while device 100 is in a locked state. In locked deviceinterface 5000-B, virtual channel 5064 is displayed with unlock object5066 (also called an “unlock image” or “unlock image object”) and unlockcamera object 5068 (also called an “unlock camera image” or “unlockcamera image object”). In some embodiments, unlock object 5066 andunlock camera object 5068 are displayed in opposite ends of virtualchannel 5064. For example, as shown in FIG. 5G, unlock object 5066 isdisplayed at the left end of virtual channel 5064, and unlock cameraobject 5068 is displayed at the right end of virtual channel 5064.

In some embodiments, unlock object 5066 and unlock camera object 5068,respectively, may be dragged to a location in virtual channel 5064adjacent to the respective other object. For example, FIG. 5G showsgesture 5070 detected on unlock object 5066. Gesture 5070 moves withmovement 5072 toward the right end of virtual channel 5064. In responseto the detection of gesture 5070 and corresponding movement 5072, unlockobject 5066 moves within virtual channel 5064 toward unlock cameraobject 5068, up to a location adjacent to unlock camera object 5068, asshown in FIG. 5H.

FIG. 5I shows gesture 5074 detected on unlock camera object 5068.Gesture 5074 moves with movement 5076 toward the left end of virtualchannel 5064. In response to the detection of gesture 5074 andcorresponding movement 5076, unlock camera object 5068 moves withinvirtual channel 5064 toward unlock object 5066, up to a locationadjacent to unlock object 5066, as shown in FIG. 5I.

Gesture 5070 may be released while unlock object 5066 is adjacent tounlock camera object 5068, as shown in FIG. 5H. If device 100 is in alocked, passcode-protected state when gesture 5070 is released, inresponse to the release of gesture 5070, passcode entry user interface5022 is displayed (as in FIG. 5C), and the user has to enter the correctpasscode to unlock device 100. If device 100 is in a locked,not-passcode-protected state when gesture 5070 is released, in responseto the release of gesture 5070, device 100 is unlocked, and a userinterface that was being displayed when the device was put into thelocked state (e.g., user interface 400, FIG. 4A) may be displayed ontouch screen 112.

Similarly, gesture 5074 may be released while unlock camera object 5068is adjacent to unlock object 5066, as shown in FIG. 5J. In response tothe release of gesture 5074, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session, and camera interface 5026 is displayed, as in FIG.5D. If device 100 was in a locked, not-passcode-protected state, device100 is unlocked, camera application 143 is started in an unrestrictedsession, and camera interface 5026 is displayed (as in FIG. 5D) withoutthe restrictions of a restricted session.

In some other embodiments, unlock object 5066 and unlock camera object5068, respectively, may each be dragged to the location formerlyoccupied by the respective other object (with the respective otherobject ceasing to be displayed). For example, in response to thedetection of gesture 5070 and corresponding movement 5072, unlock object5066 moves within virtual channel 5064 toward unlock camera object 5068,up to the tight end of virtual channel 5064 where unlock camera object5068 was previously located, as shown in FIG. 5K-5L. Conversely, inresponse to the detection of gesture 5074 and corresponding movement5076, unlock camera object 5068 moves within virtual channel 5064 towardunlock object 5066, up to the left end of virtual channel 5064 whereunlock object 5066 was previously located, as shown in FIGS. 5M-5N.

In some embodiments, as gesture 5070 and movement 5072 are detected,unlock camera object 5068 fades out, as shown in FIG. 5K. Conversely, asgesture 5074 and movement 5076 are detected, unlock object 5066 fadesout, as shown in FIG. 5M.

In some other embodiments, unlock object 5066 and unlock camera object5068 move in unison. As unlock object 5066 moves to the right end ofvirtual channel 5064, unlock camera object 5068, instead of fading out,moves rightward, going under the boundary of virtual channel 5064 andout of view as unlock object 5066 moves rightward, as shown in FIG. 5O.Conversely, as unlock camera object 5068 moves to the left end ofvirtual channel 5064, unlock object 5066, instead of fading out, movesleftward, going under the boundary of virtual channel 5064 and out ofview as unlock camera object 5068 moves leftward, as shown in FIG. 5P.

In some further embodiments, as unlock object 5066 moves to the rightend of virtual channel 5064, unlock camera object 5068 stays in placeand unlock object 5066 overlaps (and goes over) unlock camera object5068 as unlock object 5066 moves to the right end of virtual channel5064 (not shown). As unlock camera object 5068 moves to the left end ofvirtual channel 5064, unlock object 5066 stays in place and unlockcamera object 5068 overlaps (and goes over) unlock object 5066 as unlockcamera object 5068 moves to the left end of virtual channel 5064 (notshown).

Gesture 5070 may be released while unlock object 5066 is at the rightend of virtual channel 5064, as shown in FIG. 5L. If device 100 is in alocked, passcode-protected state, in response to the release of gesture5070, passcode entry user interface 5022 is displayed (as in FIG. 5C),and the user has to enter the correct passcode to unlock device 100. Ifdevice 100 is in a locked, not-passcode-protected state, in response tothe release of gesture 5070, device 100 is unlocked, and a userinterface that was being displayed when the device was put into thelocked state (e.g., user interface 400, FIG. 4A) may be displayed ontouch screen 112.

Gesture 5074 may be released while unlock camera object 5068 at the leftend of virtual channel 5064, as shown in FIG. 5N. In response to therelease of gesture 5074, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session, and camera interface 5026 is displayed, as in FIG.5D. If device 100 was in a locked, not-passcode-protected state, device100 is unlocked, camera application 143 is started in an unrestrictedsession, and camera interface 5026 is displayed (as in FIG. 5D) withoutthe restrictions of a restricted session.

From camera interface 5026, camera roll image viewer interface 5042 andcamera roll thumbnails interface 5056 may be accessed, as describedabove with reference to FIGS. 5D-5F. For brevity, the details are notrepeated here.

FIG. 5Q illustrates locked device interface 5000-C displayed on touchscreen 112 while device 100 is in a locked state. In locked deviceinterface 5000-C, virtual channel 5080 is displayed with unlock object5078 displayed at the left end of virtual channel 5080. Gesture 5082 andits corresponding movement 5084 may be detected on unlock object 5078.In response to the detection of gesture 5082 and movement 5084, unlockobject 5078 moves within virtual channel 5080 in accordance with thedirection of movement 5084, up to the right end of virtual channel 5080.

Gesture 5082 may be released while unlock object 5078 is at the rightend of virtual channel 5084. If device 100 is in a locked,passcode-protected state, in response to the release of gesture 5082,passcode entry user interface 5022 is displayed (as in FIG. 5C), and theuser has to enter the correct passcode to unlock device 100. If device100 is in a locked, not-passcode-protected state, in response to therelease of gesture 5082, device 100 is unlocked, and a user interfacethat was being displayed when the device was put into the locked state(e.g., user interface 400, FIG. 4A) may be displayed on touch screen112.

Locked device interface 5000-C also includes predefined region 5086.Multiple page indicators 5088 are displayed in region 5086. The pageindicators 5088 indicate that the user may perform a gesture on region5086 to switch between “pages.” For example, the “page” displayed inFIG. 5Q is the second of three “pages”; indicator 5088-B is colored orhighlighted differently from the other indicators 5088-A and 5088-C. Insome embodiments, the second “page” includes information such as thecurrent time and date, as shown in FIG. 5Q.

In some embodiments, one or more of the page indicators 5088 are shapedto indicate an association with a respective application. For example,indicator 5088-C is shaped like a camera, to indicate that the third“page” is associated with camera application 143 or camera functionalityon device 100 in some way.

A substantially horizontally moving gesture may be detected on region5086. For example, in FIG. 5Q, gesture 5090 with movement 5092 may bedetected on region 5086 while the second “page” is displayed. Inresponse to the detection of gesture 5090 and corresponding movement5092, a first “page” is displayed on touch screen 112 in place of thesecond “page,” as shown in FIG. 5R. In accordance with the page change,indicators 5088-A and 5088-B changes color or highlighting to indicatethat the first “page” is currently displayed. In some embodiments, thefirst “page” includes media playback controls 5090 (e.g., play/pause,next track, previous track, etc.) and volume indicator bar 5091. Whilethe first “page” is displayed, if a gesture that is similar to gesture5090 but moving in a direction opposite of movement 5092 is detected,the second “page” is displayed in response.

Returning to FIG. 5Q, gesture 5094 with movement 5096 may be detected onregion 5086 while the second “page” is displayed. Movement 5096 has adirection opposite of movement 5090. In response to the detection ofgesture 5094 and movement 5096, a third “page” is displayed in place ofthe second “page,” as shown in FIG. 5S. In accordance with the pagechange, indicators 5088-B and 5088-C changes color or highlighting toindicate that the third “page” is currently displayed. While the third“page” is displayed, if a gesture that is similar to gesture 5094 butmoving in a direction opposite of movement 5096 is detected, the second“page” is displayed in response.

The third “page” displayed on touch screen 112 includes camera icon5098, as shown in FIG. 5S. A gesture (e.g., tap gesture 5100) may bedetected on camera icon 5098. In response to the detection of gesture5100 on icon 5098, if device 100 was in a locked, passcode-protectedstate, camera application 143 is started in a restricted session andcamera interface 5026 is displayed, as in FIG. 5D. If device 100 was ina locked, not-passcode-protected state, device 100 is unlocked, cameraapplication 143 is started in an unrestricted session, and camerainterface 5026 is displayed (as in FIG. 5D) without the restrictions ofa restricted session. From camera interface 5026, camera roll imageviewer interface 5042 and camera roll thumbnails interface 5056 areaccessible, as described above with reference to FIGS. 5D-5F. Forbrevity, these details are not repeated here.

FIG. 5T illustrates locked device interface 5000-D displayed on touchscreen 112 while device 100 is in a locked state. In locked deviceinterface 5000-D, virtual channel 5080 is displayed with unlock object5078 displayed at the left end of virtual channel 5080. Unlock object5078 may be interacted with using gestures (e.g., gesture 5082, FIG. 5Q)to unlock device 100. For brevity, the details are not repeated here.

Locked device interface 5000-D also includes predefined region 5102.Multiple page indicators 5104 are displayed in region 5102. The pageindicators 5104 indicate that the user may perform a gesture on region5102 to switch between “pages.” For example, the “page” displayed inFIG. 5T is the second of three “pages”; indicator 5104-B is colored orhighlighted differently from the other indicators 5104-A and 5104-C. Insome embodiments, the second “page” includes information such as thecurrent time and date, as shown in FIG. 5T.

In some embodiments, one or more of the page indicators 5104 are shapedto indicate an association with a respective application. For example,indicator 5104-A is shaped like a camera, to indicate that a first“page” is associated with camera application 143 or camera functionalityon device 100 in some way.

A substantially horizontally moving gesture may be detected on region5102. For example, in FIG. 5T, gesture 5106 with movement 5108 may bedetected on region 5102 while the second “page” is displayed. Inresponse to the detection of gesture 5106 and corresponding movement5108, camera application 143 is started in a restricted session andcamera interface 5026 is displayed, as in FIG. 5D, in place of lockeddevice interface 5000-D. In some embodiments, while camera interface5026 is displayed, if a gesture that is similar to gesture 5106 butmoving in a direction opposite of movement 5108 is detected, in responsethe second “page” (i.e., locked device interface 5000-D as shown in FIG.5T) is displayed.

Returning to FIG. 5T, gesture 5110 with movement 5112 may be detected onregion 5102 while the second “page” is displayed. In response to thedetection of gesture 5110 and corresponding movement 5112, a third“page” is displayed on touch screen 112 in place of the second “page,”as shown in FIG. 5U. In accordance with the page change, indicators5104-B and 5104-C changes color or highlighting to indicate that thethird “page” is currently displayed. In some embodiments, the third“page” includes media playback controls 5090 (e.g., play/pause, nexttrack, previous track, etc.) and volume indicator bar 5091. While thethird “page” is displayed, if a gesture that is similar to gesture 5110but moving in a direction opposite of movement 5112 is detected, inresponse the second “page” is displayed.

FIG. 5V illustrates locked device interface 5000-E displayed on touchscreen 112. Locked device interface 5000-E includes unlock object 5078and channel 5080, which are described above with reference to FIG. 5Q,and the details are not repeated here. Locked device interface 5000-Ealso includes region 5114, where information such as the current dateand time may be displayed.

Region 5114 also includes unlock camera object 5116, as shown in FIG.5V. FIG. 5V also shows a contact corresponding to gesture 5118 detectedon unlock camera object 5116. In response to the detection of thecontact corresponding to gesture 5118, virtual channel 5119 is displayedwith unlock camera object 5116 at the left end, to indicate that unlockcamera object 5116 may be dragged to the right end of channel 5119, asshown in FIG. 5W. In response to gesture 5118 moving in direction 5220toward the right end of channel 51129, unlock camera object 5116 movestoward the right end of channel 5119 in accordance with movement 5220.When unlock camera object 5116 is at the right end of channel 5119 andgesture 5118 is released, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session and camera interface 5026 is displayed, as in FIG.5D. If device 100 was in a locked, not-passcode-protected state, device100 is unlocked, camera application 143 is started in an unrestrictedsession, and camera interface 5026 is displayed (as in FIG. 5D) withoutthe restrictions of a restricted session.

FIG. 5X illustrates locked device interface 5000-F. Locked deviceinterface 5000-F includes unlock object 5078 and virtual channel 5080,as well as unlock camera object 5224 and virtual channel 5222. Unlockcamera object 5224 is initially positioned near or at the center ofchannel 5222. At the ends of channel 5222 are still camera icon 5226 andvideo camera icon 5228, respectively. Still camera icon 5226 correspondsto a still image capture mode for camera application 143. Video cameraicon 5228 corresponds to a video capture mode for camera application143.

Gesture 5230 may be detected on unlock camera object 5222 and moveeither with movement 5232 toward still camera icon 5226 or with movement5234 toward video camera icon 5228. in response to the detection ofgesture 5230 and movement 5232, unlock camera object 5224 moves withinchannel 5222 toward still camera icon 5226 in accordance with movement5232. In response to the detection of gesture 5230 and movement 5234,unlock camera object 5224 moves within channel 5222 toward video cameraicon 5228 in accordance with movement 5234.

Gesture 5230 may be released when unlock camera object 5224 is locatedat either end of channel 5222. If gesture 5230 is released when unlockcamera object 5224 is located at the end of channel 5222 that has stillcamera icon 5226 and device 100 was in a locked, passcode-protectedstate, camera application 143 is started in a restricted session andcamera interface 5026 is displayed in still image capture mode, as inFIG. 5D. If gesture 5230 is released when unlock camera object 5224 islocated at the end of channel 5222 that has still camera icon 5226 anddevice 100 was in a locked, not-passcode-protected state, device 100 isunlocked, camera application 143 is started in an unrestricted session,and camera interface 5026 is displayed (as in FIG. 5F) in still imagecapture mode without the restrictions of a restricted session. Ifgesture 5230 is released when unlock camera object 5224 is located atthe end of channel 5222 that has video camera icon 5228 and device 100was in a locked, passcode-protected state, camera application 143 isstarted in a restricted session and camera interface 5026 is displayedin video capture mode. If gesture 5230 is released when unlock cameraobject 5224 is located at the end of channel 5222 that has video cameraicon 5228 and device 100 was in a locked, not-passcode-protected state,device 100 is unlocked, camera application 143 is started in anunrestricted session, and camera interface 5026 is displayed (as in FIG.5D) in video capture mode without the restrictions of a restrictedsession.

FIG. 5Y illustrates locked device interface 5000-G, which is similar tolocked device interface 5000-F, but with a smaller unlock camera object5238, channel 5236, still camera icon 5040, and video camera icon 5242.Unlock camera object 5238 may be interacted with in a similar manner asunlock camera object 5224 (FIG. 5X) to access camera interface 5026 instill image capture mode or video capture mode.

FIG. 5Z illustrates locked device interface 5000-H. Locked device 5000-Hincludes virtual channel 5244 and unlock object 5246 at the left end ofvirtual channel 5244, as well as unlock camera object 5248.

Gesture 5250, with corresponding movement 5252, may be detected onunlock object 5246. In response to the detection of gesture 5250 andmovement 5252, unlock object 5246 moves toward the right end of channel5244. When unlock object 5246 is at the right end of channel 5244 andgesture 5250 is released, if device 100 is in a lockedpasscode-protected state, passcode entry user interface 5022 isdisplayed, as in FIG. 5C.

Conversely, gesture 5254 may be detected on unlock camera object 5248,as shown in FIG. 5AA. In response to the detection of the contactcorresponding to gesture 5254 on unlock camera object 5248, an animationshowing channel 5244 decreasing in length and virtual channel 5256appearing and lengthening may be displayed, an instant of which isillustrated in FIG. 5BB. The animation continues as long as the contactcorresponding to gesture 5254 continues to be detected on unlock cameraobject 5248. When the animation is complete, channel 5244 ceases to bedisplayed and channel 5256 is displayed at its full length, with unlockcamera object 5248 at the right end of channel 5256, as shown in FIG.5CC.

While gesture 52S 4 is detected on unlock camera object 5248, gesture5254 may move toward the left end of channel 5256, as shown in FIG. 5CC.In response to the detection of movement 5258, unlock camera object 5248moves toward the left end of channel 5256 in accordance with movement525$. When unlock camera object 5248 is at the left end of channel 5256and gesture 5254 is released, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session and camera interface 5026 is displayed, as in FIG.5D. If device 100 was in a locked, not-passcode-protected state, device100 is unlocked, camera application 143 is started in an unrestrictedsession, and camera interface 5026 is displayed (as in FIG. 5D) withoutthe restrictions of a restricted session.

FIG. 5DD illustrates locked device interface 5000-I displayed on touchscreen 112. Locked device interface 5000-I includes virtual channel 5260and unlock object 5262 located at the left end of virtual channel 5260.

Gesture 5264 and corresponding movement 5266 may be detected on unlockobject 5262. In response to the detection of gesture 5264 andcorresponding movement 5266, unlock object 5262 moves toward the rightend of channel 5260 in accordance with movement 5266, as shown in FIG.5EE.

When unlock object 5264 moves from the left end of channel 5260 to aboutthe middle of channel 5260, camera icon 5268 may be displayed at theleft end of channel 5260. At this point, gesture 5264 may continue tomove with movement 5266 toward the right end of channel 5260 or reversedirection and move with movement 5270 toward the left end of channel5260.

When unlock object 5264 is at the tight end of channel 5260 after movingthere in accordance with movement 5266 and then gesture 5264 isreleased, if device 100 is in a locked, passcode-protected state,passcode entry user interface 5022 is displayed, as in FIG. 5C.

When unlock object 5264 is back at the left end of channel 5260 aftermoving there in accordance with movement 5270 and then gesture 5264 isreleased (as shown in FIG. 5FF), if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session and camera interface 5026 is displayed, as in FIG.5D. If device 100 was in a locked, not-passcode-protected state, device100 is unlocked, camera application 143 is started in an unrestrictedsession, and camera interface 5026 is displayed (as in FIG. 5D) withoutthe restrictions of a restricted session.

FIG. 5GG illustrates locked device interface 5000-J displayed on touchscreen 112 of device 100. Locked device interface 5000-J, as with theother locked device interfaces 5000 described above, may be displayedwhen a physical button (e.g., push button 206, home or menu button 204)on device 100 is activated by a user while device 100 is in a lockedstate. Locked device interface 5000-J may include a message informingthe user that the device is locked, as well as other information (e.g.,current time and date).

Locked device interface 5000-J includes unlock object 5276 and virtualchannel 5274, and camera access indicia 5006. Camera access indicia 5006includes icons 5008 and 5010, which are described above with referenceto FIG. 5A. Unlock object 5276, channel 5274, and camera access indicia5006 may be displayed in predefined region 5272.

Gesture 5278 may be detected on unlock object 5276. Gesture 5278 moveswith movement 5280. In response to the detection of gesture 5278 andcorresponding movement 5280, unlock object 5276 moves within virtualchannel 5274 toward the right end of channel 5274. When unlock object5276 is moved to the right end of channel 5274 and then gesture 5278 isreleased, in response to the detection of the release of gesture 5278,if device 100 is in a locked, passcode-protected state, passcode entryuser interface 5022 is displayed, as in FIG. 5C.

Gesture 5282 may be detected on camera access indicia 5006. Gesture 5282moves with movement 5284. In response to the detection of gesture 5282and a determination that gesture 5282 starts on camera access indicia5006, if device 100 was in a locked, passcode-protected state, region5272 expands (e.g., in an animation) in accordance with the direction ofmovement 5284, as shown in FIG. 5HH, and transitions into camerainterface 5026 (FIG. 5D) of camera application 143 starting in arestricted session. When movement 5284 is complete (e.g., reaches thetop of touch screen 112) and gesture 5282 is released, locked deviceinterface 5000-J ceases to be displayed, and camera interface 5026 isdisplayed in a restricted session for camera application 143 on touchscreen 112. In response to the detection of gesture 5282 and adetermination that gesture 5282 starts on camera access indicia 5006, ifdevice 100 was in a locked, not-passcode-protected state, region 5272expands (e.g., in an animation) in accordance with the direction ofmovement 5284, as shown in FIG. 5HH, and transitions into camerainterface 5026 (FIG. 5D) of camera application 143 starting in anunrestricted session. When movement 5284 is complete (e.g., reaches thetop of touch screen 112) and gesture 5282 is released, locked deviceinterface 5000-J ceases to be displayed, and camera interface 5026 isdisplayed in an unrestricted session for camera application 143 on touchscreen 112.

In some embodiments, a gesture (e.g. tap gesture 5304, FIG. 5KK) may beperformed on camera access indicia 5006 (FIG. 5KK). In response to thedetection of a tap gesture on camera access indicia 5006, an animationof locked device interface 5000-J may be displayed (e.g., FIGS.5LL-5NN). In the animation, locked device interface 5000-J moves ortranslates, as if it is bouncing off the bottom edge of touch screen112, to partially reveal an interface corresponding to cameraapplication 143 (e.g., camera interface 5026, FIG. 5MM) and then returnsto its position prior to the animation. The partial reveal in responseto detection of the gesture provides a user with an indication that theuser may interact with camera access indicia 5006 (e.g., by performinggesture 5016 or 5282) to launch camera application 143.

Alternatively, locked camera interface 5000-J may include camera icon5286 instead of camera access indicia 5006, as shown in FIG. 5II. Inresponse to the detection of a gesture (e.g., tap gesture 5288) oncamera icon 5286, if device 100 was in a locked, passcode-protectedstate, camera application 143 is started in a restricted session andcamera interface 5026 is displayed, as in FIG. 5D. In response to thedetection of a gesture (e.g., tap gesture 5288) on camera icon 5286, ifdevice 100 was in a locked, not-passcode-protected state, device 100 isunlocked, camera application 143 is started in an unrestricted session,and camera interface 5026 is displayed (as in FIG. 5D) without therestrictions of a restricted session.

FIG. 5JJ illustrates locked device interface 5000-K displayed on touchscreen 112. Locked device interface 5000-K includes virtual channel 5290and unlock object 5292 located near or at the middle of channel 5290. Atthe ends of channel 5290 are camera icon 5294 and lock icon 5296,respectively.

Gesture 5298 may be detected on unlock object 5292 and move either withmovement 5302 toward camera icon 5294 or with movement 5300 toward lockicon 5296. In response to the detection of gesture 5298 and movement5302, unlock object 5292 moves within channel 5290 toward camera icon5294 in accordance with movement 5302. In response to the detection ofgesture 5298 and movement 5300, unlock object 5292 moves within channel5290 toward lock icon 5296 in accordance with movement 5300.

Gesture 5298 may be released when unlock object 5292 is located ateither end of channel 5290. If gesture 5298 is released when unlockobject 5292 is located at the end of channel 5290 that has camera icon5294 and device 100 was in a locked, passcode-protected state, cameraapplication 143 is started in a restricted session and camera interface5026 is displayed in still image capture mode, as in FIG. 5D. If gesture5298 is released when unlock object 5292 is located at the end ofchannel 5290 that has camera icon 5294 and device 100 was in a locked,not-passcode-protected state, device 100 is unlocked, camera application143 is started in an unrestricted session, and camera interface 5026 isdisplayed (as in FIG. 5D) without the restrictions of a restrictedsession. If gesture 5298 is released when unlock object 5292 is locatedat the end of channel 5290 that has lock icon 5296 and device 100 is ina locked, passcode-protected state, passcode entry user interface 5022is displayed, as in FIG. 5C.

FIG. 5OO illustrates locked device interface 5000-L displayed on touchscreen 112 of device 100. Locked device interface 5000-L, as with theother locked device interfaces 5000 described above, may be displayedwhen a physical button (e.g., push button 206, home or menu button 204)on device 100 is activated by a user while device 100 is in a lockedstate. Locked device interface 5000-L may include a message informingthe user that the device is locked, as well as other information (e.g.,current time and date).

Locked device interface 5000-L includes unlock object 5276 and virtualchannel 5274, and application access indicia 5406. Application accessindicia 5406 include icons 5408 and 5010. Icon 5408 indicates anapplication with which application access indicia 5406 are associated.For example, icon 5408 as shown in FIG. 5OO depicts a camera;application access indicia 5406 are associated with camera application143. Other applications that may be associated with application accessindicia 5406 include, for example, notifications application 165, emailapplication 140, or phone application 138. Icons 5010 are describedabove with reference to FIG. 5A. Unlock object 5276, channel 5274, andapplication access indicia 5406 may be displayed in predefined region5402. In some embodiments, camera icon 5416 and video icon 5418 are alsodisplayed in locked device interface 5000-L.

FIG. 5OO shows gesture 5412 detected on touch screen 112. Gesture 5412is detected as starting from application access indicia 5406. Gesture5412 moves with movement 5414 toward icon 5416. In response to thedetection of gesture 5412 and a. determination that gesture 5412 startson application access indicia 5406, locked device interface 5000-Lceases to be displayed. If device 100 was in a locked,passcode-protected state, camera application 143 (the application withwhich application access indicia 5406 is associated) is started in stillimage capture mode (as indicated by toggle switch 5032 set to stillimage mode) in a restricted session, and corresponding interface 5026 isdisplayed, as shown in FIG. 5QQ, and applications other than cameraapplication 143 are maintained in the locked, passcode-protected state.If device 100 was in a locked, not-passcode-protected state, cameraapplication 143 is started in still image mode in an unrestrictedsession, and corresponding interface 5026 is displayed. In someembodiments, interface 5026 may be revealed in an animation in whichlocked device interface 5000-L translates off-screen in accordance withthe direction of movement 5414, and interface 5026 is revealed as moreand more of interface 5000-L translates off-screen, as shown in FIG.5OO-5QQ.

FIG. 5RR shows gesture 5422 detected on touch screen 112. Gesture 5422is detected as starting from application access indicia 5406. Gesture5422 moves with movement 5424 toward icon 5418. In response to thedetection of gesture 5422 and a determination that gesture 5422 startson application access indicia 5406, locked device interface 5000-Lceases to be displayed. If device 100 was in a locked,passcode-protected state, camera application 143 (the application withwhich application access indicia 5406 is associated) is started in videocapture mode (as indicated by toggle switch 5032 set to video mode) in arestricted session, and corresponding interface 5026 is displayed, asshown in FIG. 5TT, and applications other than camera application 143are maintained in the locked, passcode-protected state. For example, inFIG. 5TT, button 5030 in interface 5026 is now a video recordingstart/pause button. If device 100 was in a locked,not-passcode-protected state, camera application 143 is started in videomode in an unrestricted session, and corresponding interface 5026 isdisplayed. In some embodiments, interface 5026 may be revealed in ananimation in which locked device interface 5000-L translates off screenin accordance with the direction of movement 5424, and interface 5026 isrevealed as more and more of interface 5000-L translates off-screen, asshown in FIG. 5RR-5TT.

In FIGS. 5OO-5TT, camera application 143 is started in differentmodes—still image mode in FIG. 5QQ and video mode in FIG. 5TT. The modein which camera application 143 is started is determined by the type ofgesture that is detected as starting on application access indicia 5406.Gesture 5412 (FIG. 5OO) and gesture 5422 (5RR) are different types ofgestures. In some embodiments, the different types of gestures includedifferent paths of movement of the contact in the gesture. For example,gesture 5412 includes movement 5414, which is a substantially verticalpath, and gesture 5422 includes movement 5424, which has a diagonal pathdistinct from the substantially vertical path of movement 5414. Inresponse to the determination that gesture 5412 is of the type with thevertical path, camera application 143 is started in still image mode. Inresponse to the determination that gesture 5422 is of the type with thediagonal path, camera application 143 is started in video mode. Asanother example, movement 5414 of gesture 5412 may have a substantiallyvertical path as shown, and movement 5424 of gesture 5422 may have asubstantially horizontal path (e.g., drag to the left or the right,depending on the specific implementation).

In some other embodiments, the different types of gestures includedifferent locations where the movement of the contact in the gestureends. For example, in gesture 5412 (FIGS. 5OO-5PP), the contact is shownas moving toward camera icon 5416, and gesture 5412 is complete when thecontact ends at the area of camera icon 5416 (e.g., at a location oftouch screen 112 over camera icon 5416). In gesture 5422 (FIGS.5RR-5SS), the contact is shown as moving toward video icon 5418, andgesture 5422 is complete when the contact ends at the area of cameraicon 5418 (e.g., at a location of touch screen 112 over camera icon5418).

In some other embodiments, the different types of gestures includedifferent numbers of contacts in the gesture. For example, gesture 5412(FIGS. 5OO-5PP) includes one contact. On the other hand, gesture 5454(FIGS. 5FFF-5GGG) includes two contacts, which move together in movement5456. In response to the detection of gesture 5454 and a determinationthat gesture 5454 starts on application access indicia 5406, lockeddevice interface 5000-L ceases to be displayed. If device 100 was in alocked, passcode-protected state, camera application 143 is started invideo mode in a restricted session, and corresponding interface 5026 isdisplayed, as in FIG. 5TT, and applications other than cameraapplication 143 are maintained in the locked, passcode-protected state.If device 100 was in a locked, not-passcode-protected state, cameraapplication 143 is started in video mode in an unrestricted session, andcorresponding interface 5026 is displayed. in some embodiments,interface 5026 may be revealed in an animation in which locked deviceinterface 5000-L translates off-screen in accordance with the directionof movement 5454, and interface 5026 is revealed as more and more ofinterface 5000-L translates off-screen.

In some embodiments, icon 5408 may change appearance based on the typeof gesture (e.g., the path of the movement of the contact in thegesture, number of contacts, etc.) detected on application accessindicia 5406. For example, when one contact is detected on applicationaccess indicia 5406, as shown in FIG. 5OO, icon 5408 shows a still imagecamera (indicating that camera application 143 will start in still imagemode if a gesture with the contact (e.g., gesture 5412) is detected).When two contacts are detected on application access indicia 5406, asshown in FIG. 5FFF, icon 5408 may be animated to show a video camerainstead of a still image camera. (indicating that camera application 143will start video mode if a gesture with the contacts (e.g., gesture5454) is detected). As another example, when movement 5424 of thecontact is detected instead of contact 5414, icon 5408 changesappearance to show a video camera, as shown in FIGS. 5RR-5SS. The changein the appearance of icon 5408 may be animated.

FIG. 5UU shows gesture 5432 detected on application access indicia 5432.Gesture 5432 is a different type of gesture than gesture 5412 andgesture 5422. In some embodiments, gesture 5432 is a tap gesture. Inresponse to the detection of gesture 5432 on application access indicia5406, an animation of locked device interface 5000-L may be displayed(e.g., FIGS. 5VV-5XX). In the animation, locked device interface 5000-Lmoves or translates to partially reveal an interface corresponding tocamera application 143 in a first mode (e.g., camera interface 5026 instill image mode) and then returns to its position prior to theanimation. The partial reveal in response to detection of gesture 5432provides a user with an indication that the user may interact withapplication access indicia 5406 (e.g., by performing gesture 5412) tolaunch camera application 143 in still image mode.

FIG. 5YY shows gesture 5438 detected on application access indicia 5406.Gesture 5438 is also a different type than gesture 5412 and gesture5422, and may be of the same type as gesture 5432 (FIG. 5UU). Inresponse to the detection of gesture 5438 on application access indicia5406, an animation of locked device interface 5000-L may be displayed(e.g., FIGS. 5ZZ-5BBB). In the animation, locked device interface 5000-Lmoves or translates to partially reveal an interface corresponding tocamera application 143 in a second mode (e.g., camera interface 5026 invideo mode) and then returns to its position prior to the animation. Thepartial reveal in response to detection of gesture 5438 provides a userwith an indication that the user may interact with application accessindicia 5406 (e.g., by performing gesture 5422) to launch cameraapplication 143 in video mode.

In some embodiments, the animation of locked device interface 5000-Lincludes translation of locked device interface 5000-L in one direction(e.g., movement 5434, FIG. VV or 5ZZ) to partially reveal interface 5026and then movement in the opposite direction (e.g., movement 5436, FIG.5XX or 5BBB) to hide interface 5026.

In some embodiments, alternating tap gestures on application accessindicia 5406 partially reveal interface 5026 in, in alternating order,still image mode and video mode. For example, detection of gesture 5432on application access indicia 5406 and a partial reveal of interface5026 in still image mode in response may be followed by detection ofgesture 5438 on application access indicia 5406 and a partial reveal ofinterface 5026 in video mode in response. Thus, tapping on applicationaccess indicia 5406 once partially reveals interface 5026 in still imagemode, and then tapping on application access indicia 5406 a second timepartially reveals interface 5026 in video mode. In some otherembodiments, a tap gesture on application access indicia 5406 with onecontact partially reveals interface 5026 in still image mode. and a tapgesture with multiple contacts (e.g., two contacts) on applicationaccess indicia 5406 partially reveals interface 5026 in video mode.

FIG. 5CCC shows gesture 5444 detected on application access indicia5406. Gesture 5444 is a different type of gesture from gestures 5412 and5422. In some embodiments, gesture 5444 is a tap-and-hold gesture. Inresponse to detection of gesture 5444 on application access indicia5406, visual indications 5446 and 5448 of gestures to start cameraapplication 143 in still image mode (e.g., gesture 5412) and video mode(e.g., gesture 5414), respectively, are displayed. The visualindications 5446 and 5448 may include text, graphics (e.g., arrows), orany combination of these.

FIG. 5EEE shows gesture 5450 detected on unlock object 5276. Gesture5450 moves with movement 5452. In response to the detection of gesture5450 and corresponding movement 5452, unlock object 5276 moves withinvirtual channel 5274 toward the right end of channel 5274. When unlockobject 5276 is moved to the right end of channel 5274 and then gesture5450 is released, in response to the detection of the release of gesture5450, if device 100 is in a locked, passcode-protected state, passcodeentry user interface 5022 is displayed, as in FIG. 5C.

FIG. 5HHH illustrates locked device interface 5000-M displayed on touchscreen 112 of device 100. Locked device interface 5000-M, as with theother locked device interfaces 5000 described above, may be displayedwhen a physical button (e.g., push button 206, home or menu button 204)on device 100 is activated by a user while device 100 is in a lockedstate. Locked device interface 5000-M may include a message informingthe user that the device is locked, as well as other information (e.g.,current time and date).

Locked device interface 5000-M includes unlock object 5276 and virtualchannel 5274, first access indicia 5458, and second access indicia 5462.First access indicia 5458 include icons 5460 and 5010. First accessindicia 5458 and second access indicia 5462 are both associated with anapplication. As shown, first access indicia 5458 and second accessindicia 5462 are associated with camera application 143. Otherapplications that may be associated with first and second access indicia5458, 5462 include, for example, notifications application 165, emailapplication 140, or phone application 138. Icon 5460 indicates a firstmode, of camera application 143, with which first access indicia 5406are associated. For example, icon 5460 as shown in FIG. 5HHH depicts astill image camera first access indicia 5406 are associated with a stillimage capture mode of camera application 143. Icons 5010 are describedabove with reference to FIG. 5A. Unlock object 5276, channel 5274, andapplication access indicia 5406 may be displayed in predefined region5457. In some embodiments, camera icon 5416 and video icon 5418 are alsodisplayed in locked device interface 5000-M. In some embodiments, cameraicon 5416 and video icon 5418 are not displayed in locked deviceinterface 5000-M.

FIG. 5HHH shows gesture 5466 detected on touch screen 112. Gesture 5466is detected as starting from first access indicia 5458. Gesture 5466moves with movement 5468. In response to the detection of gesture 5466and a determination that gesture 5466 starts on first access indicia5458. locked device interface 5000-M ceases to be displayed. If device100 was in a locked, passcode-protected state, camera application 143(the application with which first access indicia 5458 is associated) isstarted in still image capture mode (as indicated by toggle switch 5032set to still image mode) in a restricted session, and correspondinginterface 5026 is displayed, as shown in FIG. 5JJJ, and applicationsother than camera application 143 are maintained in the locked,passcode-protected state. If device 100 was in a locked,not-passcode-protected state, camera application 143 is started in stillimage mode in an unrestricted session, and corresponding interface 5026is displayed. In some embodiments, interface 5026 may be revealed in ananimation in which locked device interface 5000-M translates off-screenin accordance with the direction of movement 5468, and interface 5026 isrevealed as more and more of interface 5000-M translates off-screen, asshown in FIG. 5HHH-5JJJ.

FIG. 5KKK shows gesture 5470 detected on touch screen 112. Gesture 5470is detected as starting from second access indicia 5462. Gesture 5470moves with movement 5472. In response to the detection of gesture 5470and a determination that gesture 5470 starts on second access indicia5462, locked device interface 5000-M ceases to be displayed. If device100 was in a locked, passcode-protected state, camera application 143(the application with which application access indicia 5406 isassociated) is started in video capture mode (as indicated by toggleswitch 5032 set to video mode) in a restricted session, andcorresponding interface 5026 is displayed, as shown in FIG. 5MMM, andapplications other than camera application 143 are maintained in thelocked, passcode-protected state. If device 100 was in a locked,not-passcode-protected state, camera application 143 is started in videomode in an unrestricted session, and corresponding interface 5026 isdisplayed. In some embodiments, interface 5026 may be revealed in ananimation in which locked device interface 5000-M translates off-screenin accordance with the direction of movement 5472, and interface 5026 isrevealed as more and more of interface 5000-M translates off-screen, asshown in FIG. 5KKK-5MMM.

In FIGS. 5HHH-5MMM, camera application 143 is started in differentmodes—still image mode in FIG. 5JJJ and video mode in FIG. 5MMM. Themode in which camera application 143 is started is determined by theaccess indicia from which the detected gesture starts. Gesture 5466(FIG. 5HHH) starts from first access indicia 5458, and accordinglycamera application 143 is started in still image mode. Gesture 5470(5KKK) starts from second access indicia 5462, and accordingly cameraapplication 143 is started in video mode.

FIG. 5NNN illustrates another example for starting camera application143 in video mode with a gesture detected on second access indicia 5462.FIG. 5NNN shows gesture 5470, which starts on second access indicia5462, with movement 5474 that is substantially horizontal, instead ofthe substantially vertical movement 5472. In response to detection ofgesture 5470 with movement 5474, locked device interface 5000-M ceasesto be displayed. If device 100 was in a locked, passcode-protectedstate, camera application 143 (the application with which applicationaccess indicia 5406 is associated) is started in video capture mode (asindicated by toggle switch 5032 set to video mode) in a restrictedsession, and corresponding interface 5026 is displayed, as in FIG. 5MMM,and applications other than camera application 143 are maintained in thelocked, passcode-protected state. If device 100 was in a locked,not-passcode-protected state, camera application 143 is started in videomode in an unrestricted session, and corresponding interface 5026 isdisplayed. In some embodiments, interface 5026 may be revealed in ananimation in which locked device interface 5000-M translates off-screenin accordance with the direction of movement 5472, and interface 5026 isrevealed as more and more of interface 5000-M translates off-screen, asshown in FIG. 5OOO.

Gestures 5466 and 5470 may be of different types. In some embodiments,the different types of gestures include different paths of movement ofthe contact in the gesture. For example, gesture 5470 as shown in FIG.5NNN includes a substantially horizontal movement 5472, and gesture 5466includes a substantially vertical movement 5468.

In some other embodiments, the different types of gestures includedifferent locations where the movement of the contact in the gestureends. For example, in gesture 5466 (FIGS. 5HHH-5III), the contact isshown as moving toward camera icon 5416, and gesture 5466 is completewhen the contact ends at the area of camera icon 5416 (e.g., at alocation of touch screen 112 over camera icon 5416). In gesture 5470(FIGS. 5KKK-5LLL), the contact is shown as moving toward video icon5418, and gesture 5470 is complete when the contact ends at the area ofcamera icon 5418 (e.g., at a location of touch screen 112 over cameraicon 5418).

In some other embodiments, the different types of gestures includedifferent numbers of contacts in the gesture. For example, gesture 5466(FIG. 5PPP) includes one contact. On the other hand, gesture 5478 (FIG.5PPP) includes two contacts, which move together in movement 5478.Camera application 143 is started, and interface 5026 is displayed, invideo mode in response to the detection of gesture 5476 in a similarmanner as in response to gesture 5470 (FIG. 5KKK).

FIG. 5QQQ illustrates gesture 5480, which is detected on first accessindicia 5458. Gesture 5480 is a different type of gesture from gesture5466. In some embodiments, gesture 5480 is a tap gesture. In response tothe detection of gesture 5480 on first access indicia 5458, an animationof locked device interface 5000-M may be displayed (e.g., FIG. 5RRR). Inthe animation, locked device interface 5000-M moves or translates in onedirection (e.g., direction 5484) to partially reveal an interfacecorresponding to camera application 143 in a first mode (e.g., camerainterface 502.6 in still image mode) and then in the opposite direction(e.g., direction 5486) to return to its position prior to the animation.The partial reveal in response to detection of gesture 5480 provides auser with an indication that the user may interact with first accessindicia 5458 (e.g., by performing gesture 5466) to launch cameraapplication 143 in still image mode.

FIG. 5QQQ also illustrates gesture 5482, which is detected on secondaccess indicia 5462. Gesture 5482 is a different type of gesture fromgesture 5470 or 5476. In some embodiments, gesture 5482. is a tapgesture. In response to the detection of gesture 5482 on second accessindicia 5462, an animation of locked device interface 5000-M may bedisplayed (e.g., FIG. 5SSS). In the animation, locked device interface5000-M moves or translates in one direction (e.g., direction 5488) topartially reveal an interface corresponding to camera application 143 ina second mode (e.g., camera interface 5026 in video mode) and then inthe opposite direction (e.g., direction 5490) to return to its positionprior to the animation. In some embodiments, direction 5488 isorthogonal to direction 5484, and direction 5490 is orthogonal todirection 5486. The partial reveal in response to detection of gesture5482 provides a user with an indication that the user may interact withsecond access indicia 5462 (e.g., by performing gesture 5470) to launchcamera application 143 in video mode.

FIG. 5TTT shows gesture 5492 detected on unlock object 5276. Gesture5492 moves with movement 5494. In response to the detection of gesture5492 and corresponding movement 5494, unlock object 5276 moves withinvirtual channel 5274 toward the right end of channel 5274. When unlockobject 5276 is moved to the right end of channel 5274 and then gesture5492 is released, in response to the detection of the release of gesture5492, if device 100 is in a locked, passcode-protected state, passcodeentry user interface 5022 is displayed, as in FIG. 5C.

In FIGS. 5OO-5TTT described above, application access indicia 5406,first access indicia 5458, and second access indicia 5462 are associatedwith camera application 143. It should be appreciated that in someembodiments, these access indicia may be associated with otherapplications, such as notifications application 165, email application140, or phone application 138. In embodiments where the access indiciaare associated with notification application 165, the first mode may bean incoming messages notifications mode, in which notifications ofincoming messages (e.g., text messages, emails, voicemails, missedcalls) are displayed; and the second mode may be an aggregatenotifications mode, in which the notifications of incoming messages andother notifications (e.g., calendar appointments, tasks, reminders,notifications from other applications) are displayed.

In embodiments where the access indicia are associated with emailapplication 140, the first mode may be an inbox mode, in which receivedemail messages in one or more email inboxes are displayed; and thesecond mode may be an email composition mode, in which an interface forcomposing an email message is displayed.

In embodiments where the access indicia are associated with phoneapplication 138, the first mode may be a keypad mode, in which a keypadfor entering a phone number for dialing is displayed; and the secondmode may be a recent calls listing or call log mode, in which a log ofreceived, dialed, and missed calls is displayed. Alternatively, thesecond mode may be a voicemail mode, in which a listing of voicemailsare displayed and the voicemails may be played back.

FIGS. 6A-6B are flow diagrams illustrating a method 600 of accessing acamera application in a locked device in accordance with someembodiments. The method 600 is performed at a portable multifunctiondevice (e.g., device 300, FIG. 3, or portable multifunction device 100,FIG. 1) with a display, a touch-sensitive surface, and a plurality ofapplications, including a camera application. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onthe display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 600 may be combinedand/or the order of some operations may be changed.

As described below, the method 600 provides an intuitive way to quicklyaccess a camera application in a locked device. The method reduces thecognitive burden on a user when accessing a camera application in alocked device, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toaccess a camera application in a locked device faster and moreefficiently conserves power and increases the time between batterycharges.

While the device is in a locked, passcode-protected state (602), thedevice displays (604) a lock screen interface on the touch-sensitivedisplay, the lock screen interface including a camera access indicia(e.g., an icon or other graphic indicative of the camera application,such as indicia 5006 in FIG. 5A). For example, while device 100 is in alocked, passcode-protected state, locked device interface 5000-A isdisplayed on touch screen 112, as shown in FIG. 5A. Locked deviceinterface 5000-A includes camera access indicia 5006.

In some embodiments, the camera access indicia is displayed in apredefined area of the lock screen interface (606). For example, asshown in FIG. 5A, camera access indicia 5006 is displayed in region 5012in locked device interface 5000-A.

The device detects (608) a gesture on the touch-sensitive display. Forexample, in FIG. 5A, a gesture (gesture 5014 or 5018, which are gesturesof the same type with the same direction of movement, but which startfrom different locations) is detected.

In some embodiments, the gesture is a single finger slide gesture (610).For example, gesture 5014 moving with movement 5016 (FIG. 5A) may be asingle finger slide gesture.

In some embodiments, the gesture includes continuous movement of asingle finger in a predefined direction (612). Gesture 5014 (FIG. 5A),for example, is a gesture with continuous movement 5016 of a singlefinger in a predefined direction (vertically upward on display 112).

In some embodiments, the gesture includes continuous movement of asingle finger along any desired path (614).

In some embodiments, the gesture is a single finger tap gesture (616).For example, instead of gesture 5014 with movement 5016 or gesture 5018with movement 5020, the gesture may be a single finger tap gesture oncamera access indicia 5006 or away from camera access indicia 5006 (notshown).

In response to a determination that the gesture starts on the cameraaccess indicia (or, in some embodiments, on a hidden hit region for thecamera access indicia, such as a hidden hit region that surrounds thecamera access indicia) (618), the device ceases (620) to display thelock screen interface, starts (622) a restricted session for the cameraapplication, displays (624) an interface for the camera application,without displaying a passcode entry interface, and maintains (626) thedevice in the locked, passcode-protected state for applications in thedevice other than the camera application. Returning to FIG. 5A, forexample, in response to a determination that the gesture (gesture 5014)starts on camera access indicia 5006, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session and locked device interface 5000-A is replaced withcamera interface 5026 without displaying passcode entry user interface5022 (FIG. 5C). The other applications on device 100 (e.g., notes 153,browser 147, etc.) are maintained in a locked, passcode-protected state.

In some embodiments, ceasing to display the lock screen interface anddisplaying the interface for the camera application includes an animatedtransition, such as: sliding the lock screen interface off screen toreveal the interface for the camera application, sliding the lock screeninterface off screen while sliding the interface for the cameraapplication on screen, or flipping the lock screen interface around intothe interface for the camera application. For, example, an animationshowing region 5012 expanding (FIG. 5B) and transitioning into camerainterface 5026 may be displayed.

In response to a determination that the gesture starts at a location onthe touch-sensitive display other than the camera access indicia, thedevice displays (628) a passcode entry interface. In response to entryof a correct passcode in the passcode entry interface, the passcodeentry interface ceases to be displayed and the device enters an unlockedstate with access to the plurality of applications. Returning to FIG.5A, for example, in response to a determination that the gesture (e.g.,gesture 5018) starts on a location other than camera access indicia5006, if device 100 was in a locked, passcode-protected state, passcodeentry user interface 5022 is displayed (FIG. 5C). Device 100 is unlockedif the correct passcode is entered in passcode entry user interface5022.

Thus, the same gesture will produce two different results, depending onthe starting location of the gesture. For example, single finger slidegesture 5014 (FIG. 5A), which starts on camera access indicia 5006,bypasses the passcode entry interface and results in immediate displayof the camera application in a restricted session. Conversely, singlefinger slide gesture 5018 (FIG. 5A), which starts away from cameraaccess indicia 5006, results in immediate display of the passcode entryinterface.

In some embodiments, the passcode entry interface is displayed withoutdisplaying the interface for the camera application in response to thedetermination that the gesture starts at a location on thetouch-sensitive display other than the camera access indicia (630). Inresponse to the detection of gesture 5018 (FIG. 5A), for example,passcode entry user interface 5022 is displayed without displayingcamera interface 5026.

In some embodiments, the device initializes (632) one or more hardwarecomponents in a camera that is controlled by the camera application inresponse to the determination that the gesture starts on the cameraaccess indicia. For example, in response to the detection of gesture5014 on camera access indicia 5006, hardware components for the cameraon device 100 (e.g., optical sensor(s) 164) may be initialized.

In some embodiments, while the camera application is in the restrictedsession (634), the camera application is enabled to present one or moreimages generated by the camera application while in the restrictedsession (636), and the camera application is disabled from presentingany images in the camera application that were not generated while inthe restricted session (638). While camera application 143 is in arestricted session, images and videos captured during the restrictedsession may be viewed in the interface for camera application 143 (e.g.,in camera roll image viewer interface 5042), whereas images and videoscaptured outside of the restricted session (e.g., captured while device100 is unlocked) may not be viewed.

In some embodiments, while the device is in the locked,passcode-protected state, the device prevents (640) the device fromperforming a predefined set of actions (e.g., performing actions usingthe applications on the device) in response to detecting any contactwith the touch-sensitive display that does not correspond to thegesture.

It should be understood that the particular order in which theoperations in FIGS. 6A-6B have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to methods 700, 800, 900, 10)0, and 1100(e.g., FIGS. 7-9, 10A.-10C, 11A-11C) are also applicable in an analogousmanner to method 600 described above with respect to FIGS. 6A-6B. Forbrevity, these details are not repeated here.

FIG. 7 is a flow diagram illustrating a method 700 of accessing a cameraapplication in a locked device in accordance with some embodiments, Themethod 700 is performed at a portable multifunction device (e.g., device300, FIG. 3, or portable multifunction device 100, FIG. 1) with adisplay, a touch-sensitive surface, and a plurality of applications,including a camera application. In some embodiments, the display is atouch screen display and the touch-sensitive surface is on the display.In some embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 700 may be combined and/or the orderof some operations may be changed.

As described below, the method 700 provides an intuitive way to quicklyaccess a camera application in a locked device. The method reduces thecognitive burden on a user when accessing a camera application in alocked device, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toaccess a camera application in a locked device faster and moreefficiently conserves power and increases the time between batterycharges.

While the device is in a locked, passcode-protected state (702), thedevice displays (704) a lock screen interface on the touch-sensitivedisplay, the lock screen interface including a camera access indicia(e.g., an icon or other graphic indicative of the camera application,such as unlock camera object 5068 in FIG. 5G or camera icon 5286 in FIG.5II) and an unlock indicia (e.g., an icon or other graphic indicative ofa device unlocking functionality, such as unlock object 5066 in FIG.5G). For example, while device 100 is in a locked, passcode-protectedstate, locked device interface 5000-B is displayed on touch screen 112,as shown in FIG. 5G. Locked device interface 5000-B includes unlockobject 5066 and unlock camera object 5068.

In response to detecting a gesture that starts and ends on the cameraaccess indicia (or, in some embodiments, on a hidden hit region for thecamera access indicia, such as a hidden hit region that surrounds thecamera access indicia) (706), the device ceases (708) to display thelock screen interface, starts (710) a restricted session for the cameraapplication, displays (712) an interface for the camera application,without displaying a passcode entry interface, and maintains (714) thedevice in the locked, passcode-protected state for applications in thedevice other than the camera application. In some embodiments, thegesture that starts and ends on the camera access indicia is a tapgesture on the camera access indicia. In some embodiments, the gesturethat starts and ends on the camera access indicia is a drag gesture onthe camera access indicia that moves the camera access indicia, eitherby itself or with other objects on the lock screen.

For example, in FIG. 5I, in response to the detection of gesture 5074and corresponding gesture movement 5076 (i.e., gesture starting) onunlock camera object 5068, and a release of gesture 5074 from (i.e.,gesture ending on) unlock camera object 5068 after unlock camera object5068 is moved to a predefined location (e.g., adjacent to unlock object5066 (FIG. 5J) or to the left end of channel 5064 (FIG. 5N)), if device100 was in a locked, passcode-protected state, camera application 143 isstarted in a restricted session and locked device interface 5000-B isreplaced with camera interface 5026 without displaying passcode entryuser interface 5022 (FIG. 5D). The other applications on device 100(e.g., notes 153, browser 147, etc.) are maintained in a locked,passcode-protected state.

As another example, in FIG. 5II, in response to the detection of tapgesture 5288 on camera icon 5286, if device 100 was in a locked,passcode-protected state, camera application 143 is started in arestricted session and locked device interface 5000-J is replaced withcamera interface 5026 without displaying passcode entry user interface5022 (FIG. 5D). The other applications on device 100 (e.g, notes 153,browser 147, etc.) are maintained in a locked, passcode-protected state.

In some embodiments, ceasing to display the lock screen interface anddisplaying the interface for the camera application includes an animatedtransition, such as: sliding the lock screen interface off screen toreveal the interface for the camera application, sliding the lock screeninterface off screen while sliding the interface for the cameraapplication on screen, or flipping the lock screen interface around intothe interface for the camera application.

In response to detecting a gesture that starts at a location on thetouch-sensitive display associated with the unlock indicia, the devicedisplays (716) a passcode entry interface. In response to entry of acorrect passcode in the passcode entry interface, the passcode entryinterface ceases to be displayed and the device enters an unlocked statewith access to the plurality of applications.

For example, returning to FIGS. 5G-5N, in response to the detection ofgesture 5070 (i.e., starting) on unlock object 5066 and subsequentrelease of gesture 5070 after unlock object 5066 is moved to apredefined location (e.g., right end of channel 5064, FIG. 5L, oradjacent to unlock camera object 5068, FIG. 5H), if device 100 was in alocked, passcode-protected state, passcode entry user interface 5022 isdisplayed (FIG. 5C). Device 100 is unlocked if the correct passcode isentered in passcode entry user interface 5022. (An analogous responseoccurs for a gesture on unlock object 5276 in FIG. 5II.)

Thus, single finger slide gesture 5074 (FIG. 5I), which starts and endson unlock camera icon 5068, bypasses the passcode entry interface andresults in immediate display of the camera application in a restrictedsession. Conversely, single finger slide gesture 5070 (FIG. 5G), whichstarts on unlock object 5066, results in immediate display of thepasscode entry interface.

It should be understood that the particular order in which theoperations in FIG. 7 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to methods 600, 800, 900, 1000, and 1100(e.g., FIGS. 6A-6B, 8-9. 10A-10C, 11A-11C) are also applicable in ananalogous manner to method 700 described above with respect to FIG. 7.For example, the locked device interface 5000-B described above withreference to method 700 may have one or more of the characteristics ofthe locked device interface 5000-A described herein with reference tomethods 600. For brevity, these details are not repeated here.

FIG. 8 is a flow diagram illustrating a method 800 of accessing a cameraapplication in a locked device in accordance with some embodiments. Themethod 800 is performed at a portable multifunction device (e.g., device300, FIG. 3, or portable multifunction device 100, FIG. 1) with adisplay, a touch-sensitive surface, and a plurality of applications,including a camera application. In some embodiments, the display is atouch screen display and the touch-sensitive surface is on the display.In some embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 800 may be combined and/or the orderof some operations may be changed.

As described below, the method 800 provides an intuitive way to quicklyaccess a camera application in a locked device. The method reduces thecognitive burden on a user when accessing a camera application in alocked device, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toaccess a camera application in a locked device faster and moreefficiently conserves power and increases the time between batterycharges.

While the device is in a locked, passcode-protected state (802), thedevice displays (804) a lock screen interface on the touch-sensitivedisplay, the lock screen interface including a camera access indicia(e.g., an icon or other graphic indicative of the camera application,such as camera icon 5294 in FIG. 5JJ) and an unlock indicia (e.g., anicon or other graphic indicative of a device unlocking functionality,such as unlock icon 5296 in FIG. 5JJ). For example, while device 100 isin a locked, passcode-protected state, locked device interface 5000-K isdisplayed on touch screen 112, as shown in FIG. 5JJ. Locked deviceinterface 5000-K includes camera icon 5294 and unlock icon 5296.

In response to detecting a gesture that ends on the camera accessindicia (or, in some embodiments, on a hidden hit region for the cameraaccess indicia, such as a hidden hit region that surrounds the cameraaccess indicia) (806), the device ceases (808) to display the lockscreen interface, starts (810) a restricted session for the cameraapplication, displays (812) an interface for the camera application,without displaying a passcode entry interface, and maintains (814) thedevice in the locked, passcode-protected state for applications in thedevice other than the camera application. In FIG. 5JJ, for example,gesture 5298 is detected on unlock object 5292. Gesture 5298 may movewith movement 5302 toward camera icon 5294. In response to the detectionof movement 5302, unlock object 5292 moves toward camera icon 5294. Inresponse to a release of gesture 5298 from unlock object 5292 afterunlock object 5292 is moved to the location of (i.e., gesture ends on)camera icon 5294, if device 100 was in a locked, passcode-protectedstate, camera application 143 is started in a restricted session andlocked device interface 5000-K is replaced with camera interface 5026without displaying passcode entry user interface 5022 (FIG. 5D). Theother applications on device 100 (e.g., notes 153, browser 147, etc.)are maintained in a locked, passcode-protected state.

In some embodiments, ceasing to display the lock screen interface anddisplaying the interface for the camera application includes an animatedtransition, such as: sliding the lock screen interface off screen toreveal the interface for the camera application, sliding the lock screeninterface off screen while sliding the interface for the cameraapplication on screen, or flipping the lock screen interface around intothe interface for the camera application.

In response to detecting a gesture that ends at a location on thetouch-sensitive display associated with the unlock indicia, the devicedisplays (816) a passcode entry interface. In response to entry of acorrect passcode in the passcode entry interface, the passcode entryinterface ceases to be displayed and the device enters an unlocked statewith access to the plurality of applications. Returning to FIGS. 5JJ,Gesture 5298 may move with movement 5300 toward unlock icon 5296. Inresponse to the detection of movement 5300, unlock object 5292 movestoward unlock icon 5296. In response to a release of gesture 5298 fromunlock object 5292 after unlock object 5292 is moved to the location of(i.e., gesture ends on) unlock icon 5296, if device 100 was in a locked,passcode-protected state, passcode entry user interface 5022 isdisplayed (FIG. 5C). Device 100 is unlocked if the correct passcode isentered in passcode entry user interface 5022.

Thus, single finger slide gesture 5298 moving with movement 5302 (FIG.5JJ), which ends on camera icon 5294, bypasses the passcode entryinterface and results in immediate display of the camera application ina restricted session. Conversely, single finger slide gesture 5298moving with movement 5300 (FIG. 5JJ), which ends on unlock icon 5296,results in immediate display of the passcode entry interface.

It should be understood that the particular order in which theoperations in FIG. 8 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to methods 600, 700, 900, 1000, and 1100(e.g., FIGS. 6A-6B, 7, 9, 10A-10C, 11A-11C) are also applicable in ananalogous manner to method 800 described above with respect to FIG. 8.For example, the locked device interface 5000-K described above withreference to method 800 may have one or more of the characteristics ofthe locked device interface 5000-A described herein with reference tomethod 600. For brevity, these details are not repeated here.

FIG. 9 is a flow diagram illustrating a method 900 of accessing a cameraapplication in a locked device in accordance with some embodiments. Themethod 900 is performed at a portable multifunction device (e.g., device300, FIG. 3, or portable multifunction device 100, FIG. 1) with adisplay, a touch-sensitive surface, and a plurality of applications,including a camera application. In some embodiments, the display is atouch screen display and the touch-sensitive surface is on the display.In some embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 900 may be combined and/or the orderof some operations may be changed.

As described below, the method 900 provides an intuitive way to quicklyaccess a camera application in a locked device. The method reduces thecognitive burden on a user when accessing a camera application in alocked device, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user toaccess a camera application in a locked device faster and moreefficiently conserves power and increases the time between batterycharges.

While the device is in a locked, passcode-protected state (902), thedevice displays (904) a lock screen interface on the touch-sensitivedisplay, the lock screen interface including a camera access indicia(e.g., an icon or other graphic indicative of the camera application,such as indicia 5006 in FIG. 5KK). For example, while device 100 is in alocked, passcode-protected state, locked device interface 5000-J isdisplayed on touch screen 112, as shown in FIG. 5KK. Locked deviceinterface 5000-J includes camera access indicia 5006.

The device detects (906) a gesture on the touch-sensitive display. Forexample, in FIG. 5GG, gesture 5278 or 5282 is detected, and in FIG. 5KK,gesture 5304 is detected.

In response to a determination that the gesture starts on the cameraaccess indicia (or, in some embodiments, on a hidden hit region for thecamera access indicia, such as a hidden hit region that surrounds thecamera access indicia) and is of a first type (e.g., a tap gesture), thedevice partially reveals an interface for the camera application (908).In some embodiments, in response to the determination that the gesturestarts on the camera access indicia and is of a first type, the devicetranslates the lock screen interface (e.g., to partially reveal the aninterface for the camera application (909). For example, in FIG. 5KK, inresponse to a determination that the gesture (gesture 55304) starts oncamera access indicia 5006 and is of a first type (e.g., a tap gesture),lock screen interface 5000-J translates upward 5306, revealing a portionof camera interface 5026, as shown in FIG. 5LL. The upward translationof lock screen interface 5000-J reaches a peak, as shown in FIG. 5MM,and lock screen interface 5000-J translates downward 5308 back towardits original position on display 112, as shown in FIG. 5NN. The upwardand downward translation may be part of an animation of lock screeninterface 5000-J bouncing off the bottom edge of display 112, forexample.

In some embodiments, the device translates the lock screen interface ina first direction to partially reveal the interface for the cameraapplication and then translates the lock screen interface in a directionopposite the first direction to eliminate display of the partiallyrevealed interface of the camera application. This movement gives theuser a peek at the interface for the camera application, and indicates(hints) that a drag or swipe gesture on the camera access indicia willgive the user immediate access to the camera application.

In response to a determination that the gesture starts on the cameraaccess indicia (or, in some embodiments, on a hidden hit region for thecamera access indicia, such as a hidden hit region that surrounds thecamera access indicia) and is of a second type different from the firsttype (e.g., a drag or swipe gesture) (910), the device ceases (912) todisplay the lock screen interface, starts (914) a restricted session forthe camera application, displays (916) the interface for the cameraapplication, without displaying a passcode entry interface, andmaintains (918) the device in the locked, passcode-protected state forapplications in the device other than the camera application. Returningto FIG. 5GG, for example, in response to a determination that thegesture (gesture 5282) starts on camera access indicia 5006 and is of asecond type different from the first type (for example, gesture 5282being a drag or swipe gesture, compared to gesture 5304 being a tapgesture), if device 100 was in a locked, passcode-protected state,camera application 143 is started in a restricted session and lockeddevice interface 5000-J is replaced with camera interface 5026 withoutdisplaying passcode entry user interface 5022 (FIG. 5C). The otherapplications on device 100 (e.g., notes 153, browser 147, etc.) aremaintained in a locked, passcode-protected state.

In response to a determination that the gesture starts at a location onthe touch-sensitive display other than the camera access indicia (e.g.,a drag or swipe gesture starting on an unlock object), the devicedisplays (920) a passcode entry interface. In response to entry of acorrect passcode in the passcode entry interface, the passcode entryinterface ceases to be displayed and the device enters an unlocked statewith access to the plurality of applications. Returning to FIG. 5GG, forexample, in response to a determination that the gesture (e.g., gesture5278) starts on a location other than camera access indicia 5006 (e.g.,on unlock object 5276), if device 100 was in a locked,passcode-protected state, passcode entry user interface 5022 isdisplayed (FIG. 5C). Device 100 is unlocked if the correct passcode isentered in passcode entry user interface 5022.

It should be understood that the particular order in which theoperations in FIG. 9 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to methods 600, 700, 800, 1000, and 1100(e.g., FIGS. 6A-6B, 7, 8, 10A-10C, 11A-11C) are also applicable in ananalogous manner to method 900 described above with respect to FIG. 9.For example, the locked device interface 5000-J described above withreference to method 900 may have one or more of the characteristics ofthe locked device interface 5000-A described herein with reference tomethod 600. For brevity, these details are not repeated here.

FIGS. 10A-10C are flow diagrams illustrating a method 1000 of accessingdifferent modes of an application in a locked device in accordance withsome embodiments. The method 1000 is performed at a portablemultifunction device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1) with a display, a touch-sensitivesurface, and a plurality of applications, including a first application.In some embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 1000 may be combined and/or the order of some operations may bechanged.

As described below, the method 1000 provides an intuitive way to quicklyaccess different modes of an application in a locked device. The methodreduces the cognitive burden on a user when accessing different modes ofan application in a locked device, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to access different modes of an application in a lockeddevice faster and more efficiently conserves power and increases thetime between battery charges.

While the device is in a locked, passcode-protected state (1002), thedevice displays a lock screen interface on the touch-sensitive display,the lock screen interface including a first application access indicia(e.g., an icon or other graphic element that a user interacts with toaccess the first application) (1004). For example, FIG. 5OO showsapplication access indicia 5406 displayed in locked device interface5000-L.

The device detects a gesture on the touch-sensitive display (1006).FIGS. 5OO and 5RR show gestures 5412 and 5422, respectively, detected ontouch screen 112.

In response to a determination that the gesture starts on the firstapplication access indicia and is a first type of gesture (e.g.,vertical swipe gesture 5412 in FIG. 5OO, or a leftward swipe gesture5230 with movement 5232 in FIG. 5X)) (1008), the device ceases todisplay the lock screen interface (1010), starts a restricted sessionfor the first application in a first mode of the first application(1012), displays an interface for the first application in the firstmode, without displaying a passcode entry interface (1014), andmaintains the device in the locked, passcode-protected state forapplications in the device other than the first application (1016). Forexample, in response to detection of gesture 5412 and a determinationthat gesture 5412 starts on application access indicia 5406 and is afirst type of gesture, lock screen interface 5000-L ceases to bedisplayed, camera application 143 is started in still image mode in arestricted session and corresponding interface 5026 is displayed instill image mode, and the passcode-protected state are maintained forthe other applications in the device, as shown in FIGS. 5OO-5QQ.

In response to a determination that the gesture starts on the firstapplication access indicia and is a second type of gesture, distinctfrom the first type of gesture (e.g., horizontal swipe gesture, diagonalswipe gesture 5422 in FIG. 5RR, or a rightward swipe gesture (e.g.,gesture 5230 with movement 5234 in FIG. 5X)) (1018), the device ceasesto display the lock screen interface (1020), starts a restricted sessionfor the first application in a second mode of the first application,distinct from the first mode of the first application (1022), displaysan interface for the first application in the second mode, withoutdisplaying a passcode entry interface (1024), and maintains the devicein the locked, passcode-protected state for applications in the deviceother than the first application (1026). For example, in response todetection of gesture 5422 (or gesture 5454, FIGS. 5FFF-5GGG) and adetermination that gesture 5422 (or gesture 5454) starts on applicationaccess indicia 5406 and is a second type of gesture different from thefirst type of gesture, lock screen interface 5000-L ceases to bedisplayed, camera application 143 is started in video mode in arestricted session and corresponding interface 5026 is displayed invideo mode, and the passcode-protected state are maintained for theother applications in the device, as shown in FIGS. 5RR-5TT (or FIGS.5FFF-5GGG).

In some embodiments, in response to a determination that the gesturestarts on the first application access indicia and is a third type ofgesture (e.g., a tap gesture), distinct from the first type of gestureand the second type of gesture, the device partially reveals aninterface for the first mode of the first application or partiallyreveals an interface for the second mode of the first application(1028). For example, in response to detection of tap gestures 5432 and5438, interface 5026 is partially revealed in the still image mode andin the video mode, respectively, as shown in FIGS. 5UU-5BBB.

In some embodiments, partially revealing an interface for the first modeof the first application or partially revealing an interface for thesecond mode of the first application includes displaying an animationthat translates the lock screen interface (1030). As shown in FIGS.5UU-5BBB, for example, partial revealing of interface 5026 may includean animation of locked device interface 5000-L translating.

In some embodiments, the animation translates the lock screen interfacein a first direction to partially reveal the interface for the firstmode or the second mode of the first application and then translates thelock screen interface in a direction opposite the first direction toeliminate display of the partially revealed interface of the firstapplication (1032). As shown in FIGS. 5UU-5BBB, for example, partialrevealing of interface 5026 may include an animation of locked deviceinterface 5000-L translating in direction 5434 and then in the oppositedirection 5436.

In some embodiments, in response to a determination that the gesturestarts on the first application access indicia and is a third type ofgesture (e.g., a tap-and-hold gesture), distinct from the first type ofgesture and the second type of gesture, the device displays one or morevisual cues of the first type of gesture and the second type of gesture(1034). The visual cue(s) provide hints or reminders to the user of thefirst type of gesture and the second type of gesture. The visual cuesmay he textual, graphical or any combination thereof. For example, FIGS.5CCC-5DDD show visual indicators 5446 and 5448 of gestures displayed inresponse to detection of gesture 5444 (e.g., a tap-and-hold gesture) onapplication access indicia 5406.

In response to a determination that the gesture starts at a location onthe touch-sensitive display other than the first application accessindicia, the device displays a passcode entry interface, wherein inresponse to entry of a correct passcode in the passcode entry interface,the passcode entry interface ceases to he displayed and the deviceenters an unlocked state with access to the plurality of applications(1036). For example, in response to detection of gesture 5450 withmovement 5452 on unlock object 5276, as shown in FIG. 5EEE, passcodeentry user interface 5022 (FIG. 5C) is displayed.

In some embodiments, the first type of gesture includes a contact movingin a first path on the touch-sensitive surface, and the second type ofgesture includes a contact moving in a second path distinct from thefirst path on the touch-sensitive surface (1038). For example, gesture5412 (FIG. 5OO) has a substantially vertical path, and gesture 5422(FIG. 5RR) has a diagonal path.

In some embodiments, the first type of gesture includes a contact movingto and ending at a first region on the touch-sensitive surface, and thesecond type of gesture includes a contact moving to and ending at asecond region, distinct from the first region, on the touch-sensitivesurface (1040). For example, in some embodiments, gesture 5412 ends oncamera icon 5416, and gesture 5422 ends on video icon 5418.

In some embodiments, the first type of gesture includes a first numberof contacts, and the second type of gesture includes a second number ofcontacts different from the first number of contacts (1042). Forexample, gesture 5412 (FIG. 5OO) has one contact, and gesture 5454 (FIG.5FFF) has two contacts.

In some embodiments, the first application is a camera application, thefirst mode is a still image capture mode. and the second mode is a videocapture mode (1044). For example, FIGS. 5OO-5GGG show interface 5026 forcamera application 143 displayed in still image mode and video mode.

In some embodiments, the first application is a notificationsapplication, the first mode is an incoming messages notifications mode,and the second mode is an aggregate notifications mode (1046). Theapplication associated with application access indicia 5406 may benotifications application 165, and the different modes accessible fromlocked device interface 5000-L may include an incoming messagesnotifications mode and an aggregate notifications mode.

In some embodiments, the first application is an email application, thefirst mode is an inbox mode, and the second mode is an email compositionmode (1048). The application associated with application access indicia5406 may be email application 140, and the different modes accessiblefrom locked device interface 5000-L may include an inbox mode and anemail composition mode.

In some embodiments, the first application is a phone application, thefirst mode is a keypad mode, and the second mode is a recent callslisting mode (1050). The application associated with application accessindicia 5406 may be phone application 138, and the different modesaccessible from locked device interface 5000-L may include a keypad modeand a recent calls listing (e.g., call log) mode.

In some embodiments, the first application is a phone application, thefirst mode is a keypad mode, and the second mode is a voicemail mode(1052). The application associated with application access indicia 5406may be phone application 138, and the different modes accessible fromlocked device interface 5000-L may include a keypad mode and a voicemailmode.

In some embodiments, the device displays an animation that changes thefirst application access indicia from a first graphic that correspondsto the first mode to a second graphic, distinct from the first graphic,that corresponds to the second mode (e.g., an animation that changes acamera indicia from a still camera graphic to a video camera graphic, asshown in FIGS. 5RR-5SS) (1054).

It should be understood that the particular order in which theoperations in FIG. 10 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to methods 600, 700, 800, 900, and 1100(e.g., FIGS. 6A-6B, 7-9, 11A-11C) are also applicable in an analogousmanner to method 1000 described above with respect to FIG. 10. Forexample, the locked device interface 5000-L described above withreference to method 1000 may have one or more of the characteristics ofthe locked device interface 5000-A described herein with reference tomethod 600. For brevity, these details are not repeated here.

FIGS. 11A-11C are flow diagrams illustrating a method 1100 of accessingdifferent modes of an application in a locked device in accordance withsome embodiments. The method 1100 is performed at a portablemultifunction device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1) with a display, a touch-sensitivesurface, and a plurality of applications, including a first application.In some embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 1100 may be combined and/or the order of some operations may bechanged.

As described below, the method 1100 provides an intuitive way to quicklyaccess different modes of an application in a locked device. The methodreduces the cognitive burden on a user when accessing different modes ofan application in a locked device, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to access different modes of an application in a lockeddevice faster and more efficiently conserves power and increases thetime between battery charges.

While the device is in a locked, passcode-protected state (1102), thedevice displays a lock screen interface on the touch-sensitive display,the lock screen interface including a first access indicia for a firstmode in a first application (e.g., an icon or other graphic element thata user interacts with to access the first mode in the first application)and a second access indicia, distinct from the first access indicia, fora second mode in the first application (e.g., an icon or other graphicelement that a user interacts with to access the second mode in thefirst application) (1104). For example, FIG. 5HHH shows first accessindicia 5458 and second access indicia 5462 displayed in locked deviceinterface 5000-M.

The device detects a gesture on the touch-sensitive display (1106).FIGS. 5HHH, 5KKK, and 5NNN show gestures 5466 and 5470, respectively,detected on touch screen 112.

In response to a determination that the gesture starts on the firstaccess indicia and is a first type of gesture (e.g., vertical swipegesture 5466 in FIG. 5HHH or 5PPP, or a leftward swipe gesture (e.g.,gesture 5230 with movement 5232 in FIG. 5X)) (1108), the device ceasesto display the lock screen interface (1110), starts a restricted sessionfor the first application in a first mode of the first application(1112), displays an interface for the first application in the firstmode, without displaying a passcode entry interface (1114), andmaintains the device in the locked, passcode-protected state forapplications in the device other than the first application (1116). Forexample, in response to detection of gesture 5466 and a determinationthat gesture 5466 starts on first access indicia 5458 and is a firsttype of gesture, lock screen interface 5000-M ceases to be displayed,camera application 143 is started in still image mode in a restrictedsession and corresponding interface 5026 is displayed in still imagemode, and the passcode-protected state are maintained for the otherapplications in the device, as shown in FIGS. 5HHH-5JJJ, 5PPP.

In response to a determination that the gesture starts on the secondapplication access indicia and is a second type of gesture (e.g.,vertical swipe gesture 5470 in FIG. 5KKK, horizontal swipe gesture 5470in FIG. 5NNN, two-contact vertical swipe gesture 5476 in FIG. 5PPP, or arightward swipe gesture (e.g., gesture 5230 with movement 5234 in FIG.5X)) (1118), the device ceases to display the lock screen interface(1120), starts a restricted session for the first application in asecond mode of the first application, distinct from the first mode ofthe first application (1122), displays an interface for the firstapplication in the second mode, without displaying a passcode entryinterface (1124), and maintains the device in the locked,passcode-protected state for applications in the device other than thefirst application (1126). For example, in response to detection ofgesture 5470 (FIG. 5KKK or 5NNN) or 5476 (FIG. 5PPP) and a determinationthat gesture 5470 or 5476 starts on second access indicia 5464 and is asecond type of gesture, lock screen interface 5000-M ceases to bedisplayed, camera application 143 is started in video mode in arestricted session and corresponding interface 5026 is displayed invideo mode, and the passcode-protected state is maintained for the otherapplications in the device, as shown in FIGS. 5KKK-5PPP.

In some embodiments, in response to a determination that the gesturestarts on the first access indicia and is a type of gesture (e.g., a tapgesture) distinct from the first type of gesture, the device partiallyreveals an interface for the first mode of the first application; and,in response to a determination that the gesture starts on the secondaccess indicia and is a type of gesture (e.g., a tap gesture) distinctfrom the second type of gesture, the device partially reveals aninterface for the second mode of the first application (1128). Forexample, in response to detection of tap gesture 5480, interface 5026 ispartially revealed in still image mode by translating locked deviceinterface 5000-M in direction 5484, as shown in FIGS. 5QQQ-5RRR. Inresponse to detection of tap gesture 5482, interface 5026 is partiallyrevealed in video mode by translating locked device interface 5000-M indirection 5488, as shown in FIGS. 5QQQ and 5SSS.

In some embodiments, the type of gesture distinct from the first type ofgesture is a tap gesture, and the type of gesture distinct from thesecond type of gesture is a tap gesture (1130). For example, gestures5480 and 5482 may both be tap gestures.

In some embodiments, partially revealing an interface for the first modeof the application includes displaying an animation of the lock screeninterface translating in a first direction, and partially revealing aninterface for the second mode of the application includes displaying ananimation of the lock screen interface translating in a seconddirection, distinct from the first direction (1132). As shown in FIG.5RRR, for example, partial revealing of interface 5026 in still imagemode may include an animation of locked device interface 5000-Mtranslating in direction 5484. As shown in FIG. 5SSS, for example,partial revealing of interface 5026 in video mode may include ananimation of locked device interface 5000-M translating in direction5488, which is different from direction 5484.

In some embodiments, the second direction is orthogonal to the firstdirection (1134). For example, directions 5484 (FIG. 5RRR) and 5488(FIG. 5SSS) are orthogonal to each other.

In some embodiments, the second type of gesture is distinct from thefirst type of gesture (1136). For example, gesture 5466 (5HHH) andgesture 5470 (FIG. 5NNN) are different types of gestures—gesture 5466 isa vertical swipe gesture, and gesture 5470 in FIG. 5NNN is a horizontalswipe gesture.

In some embodiments, in response to a determination that the gesturestarts at a location on the touch-sensitive display other than the firstaccess indicia and the second access indicia, the device displays apasscode entry interface, wherein in response to entry of a correctpasscode in the passcode entry interface, the passcode entry interfaceceases to be displayed and the device enters an unlocked state withaccess to the plurality of applications (1138). For example, in responseto detection of gesture 5492 with movement 5494 on unlock object 5276,as shown in FIG. 5TTT, passcode entry user interface 5022 (FIG. 5C) isdisplayed.

In some embodiments, the first type of gesture includes a contact movingin a first path on the touch-sensitive surface, and the second type ofgesture includes a contact moving in a second path distinct from thefirst path on the touch-sensitive surface (1140). For example, gesture5466 has a substantially vertical path, and gesture 5470 in FIG. 5NNNhas a horizontal path.

In some embodiments, the first type of gesture includes a contact movingto and ending at a first region on the touch-sensitive surface, and thesecond type of gesture includes a contact moving to and ending at asecond region, distinct from the first region, on the touch-sensitivesurface (1142). For example, in some embodiments, gesture 5466 in FIGS.5HHH-5III ends on camera icon 5416 and gesture 5470 in FIGS. 5KKK-5LLLends on video icon 5418.

In some embodiments, the first type of gesture includes a first numberof contacts, and the second type of gesture includes a second number ofcontacts different from the first number of contacts (1144). Forexample, gesture 5466 has one contact, and gesture 5476 (FIG. 5PPP) hastwo contacts.

In some embodiments, the first application is a camera application, thefirst mode is a still image capture mode, and the second mode is a videocapture mode (1146). For example, FIGS. 5HHH-5TTT show interface 5026for camera application 143 displayed in still image mode and video mode.

In some embodiments, the first application is a notificationsapplication, the first mode is an incoming messages notifications mode,and the second mode is an aggregate notifications mode (1148). Forexample, the application associated with first access indicia 5458 andsecond access indicia 5462 may be notifications application 165, and thedifferent modes accessible from locked device interface 5000-M mayinclude an incoming messages notifications mode and an aggregatenotifications mode.

In some embodiments, the first application is an email application, thefirst mode is an inbox mode, and the second mode is an email compositionmode (1150). For example, the application associated with first accessindicia 5458 and second access indicia 5462 may be email application140, and the different modes accessible from locked device interface5000-M may include an inbox mode and an email composition mode.

In some embodiments, the first application is a phone application, thefirst mode is a keypad mode, and the second mode is a recent callslisting mode (1152). For example, the application associated with firstaccess indicia 5458 and second access indicia 5462 may be phoneapplication 138, and the different modes accessible from locked deviceinterface 5000-M may include a keypad mode and a recent calls listing(e.g., call log) mode.

In some embodiments, the first application is a phone application, thefirst mode is a keypad mode, and the second mode is a voicemail mode(1154). For example, the application associated with first accessindicia 5458 and second access indicia 5462 may be phone application138, and the different modes accessible from locked device interface5000-M may include a keypad mode and a voicemail mode.

It should be understood that the particular order in which theoperations in FIG. 11 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to methods 600, 700, 800, 900, and 1000(e.g., FIGS. 6A-6B, 7-9, 10A-10C) are also applicable in an analogousmanner to method 1000 described above with respect to FIG. 11. Forexample, the locked device interface 5000-M described above withreference to method 1000 may have one or more of the characteristics ofthe locked device interface 5000-A described herein with reference tomethod 600. For brevity, these details are not repeated here.

In accordance with some embodiments, FIG. 12 shows a functional blockdiagram of an electronic device 1200 configured in accordance with theprinciples of the invention as described above. The functional blocks ofthe device may be implemented by hardware, software, or a combination ofhardware and software to carry out, the principles of the invention. Itis understood by persons of skill in the art that the functional blocksdescribed in FIG. 12 may be combined or separated into sub-blocks toimplement the principles of the invention as described above. Therefore,the description herein may support any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 12, an electronic device 1200 includes atouch-sensitive display unit 1202 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a camera access indicia,and receive gestures; a plurality of applications 1204, including acamera application 1205; and a processing unit 1206 coupled to thetouch-sensitive display unit 1202 and the plurality of applications1204. In some embodiments, the processing unit includes a detecting unit1208, a ceasing unit 1210, a starting unit 1212, a display enabling unit1214, a maintaining unit 1216, an initializing unit 1218, and apreventing unit 1220.

The processing unit 1206 is configured to: while the device is in thelocked, passcode-protected state: detect a gesture on thetouch-sensitive display unit (e.g., with the detecting unit 1208); inresponse to a determination that the gesture starts on the camera accessindicia: cease to display the lock screen interface (e.g., with theceasing unit 1210), start a restricted session for the cameraapplication (e.g., with the starting unit 1212), enable display of aninterface for the camera application, without displaying a passcodeentry interface (e.g., with the display enabling unit 1214), andmaintain the device in the locked, passcode-protected state forapplications in the device other than the camera application (e.g., withthe maintaining unit 1216); and in response to a determination that thegesture starts at a location on the touch-sensitive display unit otherthan the camera access indicia, enable display of a passcode entryinterface (e.g., with the display enabling unit 1214), wherein inresponse to entry of a correct passcode in the passcode entry interface,the passcode entity interface ceases to be displayed and the deviceenters an unlocked state with access to the plurality of applications.

In some embodiments, the camera access indicia is displayed in apredefined area of the lock screen interface.

In some embodiments, the gesture is a single finger slide gesture.

In some embodiments, the gesture includes continuous movement of asingle finger in a predefined direction.

In some embodiments, the gesture includes continuous movement of asingle finger along any desired path.

In some embodiments, the gesture is a single finger tap gesture.

In some embodiments, the processing unit is configured to initialize oneor more hardware components in a camera that is controlled by the cameraapplication in response to the determination that the gesture starts onthe camera access indicia (e.g., with the initializing unit 1218).

In some embodiments, while the camera application is in the restrictedsession, the camera application is enabled to present one or more imagesgenerated by the camera application while in the restricted session, andthe camera application is disabled from presenting any images in thecamera application that were not generated while in the restrictedsession.

In some embodiments, the passcode entry interface is displayed withoutdisplaying the interface for the camera application in response to thedetermination that the gesture starts at a location on thetouch-sensitive display unit other than the camera access indicia.

In some embodiments, the processing unit is configured to, while thedevice is in the locked, passcode-protected state, prevent the devicefrom performing a predefined set of actions in response to detecting anycontact with the touch-sensitive display unit that does not correspondto the gesture with the preventing unit 1220).

In some other embodiments, an electronic device 1200 includes atouch-sensitive display unit 1202 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a camera access indiciaand an unlock indicia, and receive gestures; a plurality of applications1204, including a camera application 1205; and a processing unit 1206coupled to the touch-sensitive display unit 1202 and the plurality ofapplications 1204. In some embodiments, the processing unit includes adetecting unit 1208, a ceasing unit 1210, a starting unit 1212, adisplay enabling unit 1214, and a maintaining unit 1216.

The processing unit 1206 is configured to: while the device is in thelocked, passcode-protected state: in response to detecting a gesturethat starts and ends on the camera access indicia (e.g., with thedetecting unit 1208), cease to display the lock screen interface (e.g.,with the ceasing unit 1210), start a restricted session for the cameraapplication with the starting unit 1212), enable display of an interfacefor the camera application, without displaying a passcode entryinterface (e.g., with the display enabling unit 1214), and maintain thedevice in the locked, passcode-protected state for applications in thedevice other than the camera application (e.g., with the maintainingunit 1216); and in response to detecting a gesture that starts at alocation on the touch-sensitive display unit associated with the unlockindicia (e.g., with the detecting unit 1208), display a passcode entryinterface (e.g., with the display enabling unit 1214), wherein inresponse to entry of a correct passcode in the passcode entry interface,the passcode entry interface ceases to be displayed and the deviceenters an unlocked state with access to the plurality of applications.

In some other embodiments, an electronic device 1200 includes atouch-sensitive display unit 1202 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a camera access indiciaand an unlock indicia, and receive gestures; a plurality of applications1204, including a camera application 1205; and a processing unit 1206coupled to the touch-sensitive display unit 1202 and the plurality ofapplications 1204. In some embodiments, the processing unit includes adetecting unit 1208, a ceasing unit 1210, a starting unit 1212, adisplay enabling unit 1214, and a maintaining unit 1216.

The processing unit 1206 is configured to: while the device is in thelocked, passcode-protected state: in response to detecting a gesturethat ends on the camera access indicia (e.g., with the detecting unit1208): cease to display the lock screen interface (e.g., with theceasing unit 1210), start a restricted session for the cameraapplication (e.g., with the starting unit 1212), enable display of aninterface for the camera application, without displaying a passcodeentry interface (e.g., with the display enabling unit 1214), andmaintain the device in the locked, passcode-protected state forapplications in the device other than the camera application (e.g., withthe maintaining unit 1216); and in response to detecting a gesture thatends at a location on the touch-sensitive display unit associated withthe unlock indicia (e.g., with the detecting unit 1208), display apasscode entry interface (e.g., with the display enabling unit 1214),wherein in response to entry of a correct passcode in the passcode entryinterface, the passcode entry interface ceases to be displayed and thedevice enters an unlocked state with access to the plurality ofapplications.

In some other embodiments, an electronic device 1200 includes atouch-sensitive display unit 1202 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a camera access indicia,and receive gestures; a plurality of applications 1204, including acamera application 1205; and a processing unit 1206 coupled to thetouch-sensitive display unit 1202 and the plurality of applications1204. in some embodiments, the processing unit includes a detecting unit1208, a ceasing unit 1210, a starting unit 1212, a display enabling unit1214, a maintaining unit 1216, a translating unit 1222, and a revealingunit 1224.

The processing unit 1206 is configured to: while the device is in thelocked, passcode-protected state: detect a gesture on thetouch-sensitive display unit (e.g., with the detecting unit 1208); inresponse to a determination that the gesture starts on the camera accessindicia and is of a first type, partially reveal an interface for thecamera application (e.g., with the revealing unit 1224); in response toa determination that the gesture starts on the camera access indicia andis of a second type different from the first type: cease to display thelock screen interface (e.g., with the ceasing unit 1210), start arestricted session for the camera application (e.g., with the startingunit 1212), enable display of an interface for the camera application,without displaying a passcode entry interface (e.g., with the displayenabling unit 1214), and maintain the device in the locked,passcode-protected state for applications in the device other than thecamera application (e.g., with the maintaining unit 1216); and inresponse to a determination that the gesture starts at a location on thetouch-sensitive display unit other than the camera access indicia,enable display of a passcode entry interface (e.g., with the displayenabling unit 1214), wherein in response to entry of a correct passcodein the passcode entry interface, the passcode entry interface ceases tobe displayed and the device enters an unlocked state with access to theplurality of applications.

In some embodiments, the processing unit is configured to: in responseto the determination that the gesture starts on the camera accessindicia and is of a first type, translate the lock screen interface(e.g., with the translating unit 1222).

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 1300 configured in accordance with theprinciples of the invention as described above. The functional blocks ofthe device may be implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the invention. Itis understood by persons of skill in the art that the functional blocksdescribed in FIG. 13 may be combined or separated into sub-blocks toimplement the principles of the invention as described above. Therefore,the description herein may support any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 13, an electronic device 1300 includes atouch-sensitive display unit 1302 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a first applicationaccess indicia, and receive gestures; a plurality of applications 1304,including a first application 1305; and a processing unit 1306 coupledto the touch-sensitive display unit 1302 and the plurality ofapplications 1304. In some embodiments, the processing unit 1306includes a detecting unit 1308, a ceasing unit 1310, a starting unit1312, a display enabling unit 1314, a maintaining unit 1316, and arevealing unit 1318.

The processing unit 1306 is configured to: while the device is in alocked, passcode-protected state: detect a gesture on thetouch-sensitive display unit 1302 (e.g., with the detecting unit 1308);in response to a determination that the gesture starts on the firstapplication access indicia and is a first type of gesture, cease displayof the lock screen interface (e.g,, with the ceasing unit 1310), start arestricted session for the first application 1305 in a first mode of thefirst application 1305 (e.g., with the starting unit 1312), enabledisplay of an interface for the first application 1305 in the firstmode, without displaying a passcode entry interface (e.g., with thedisplay enabling unit 1314), and maintain the device in the locked,passcode-protected state for applications 1304 in the device other thanthe first application 1305 (e.g., with the maintaining unit 1316); andin response to a determination that the gesture starts on the firstapplication access indicia and is a second type of gesture, distinctfrom the first type of gesture, cease display of the lock screeninterface (e.g., with the ceasing unit 1310), start a restricted sessionfor the first application 1305 in a second mode of the first application1305, distinct from the first mode of the first application 1305 (e.g.,with the starting unit 1312), enable display of an interface for thefirst application 1305 in the second mode, without displaying a passcodeentry interface (e.g., with the display enabling unit 1314), andmaintain the device in the locked, passcode-protected state forapplications 1304 in the device other than the first application 1305(e.g., with the maintaining unit 1316).

In some embodiments, the processing unit 1306 is configured to: inresponse to a determination that the gesture starts on the firstapplication access indicia and is a third type of gesture, distinct fromthe first type of gesture and the second type of gesture, partiallyreveal an interface for the first mode of the first application 1305 orpartially reveal an interface for the second mode of the firstapplication 1305 (e.g., with the revealing unit 1318).

In some embodiments, partially revealing an interface for the first modeof the first application 1305 or partially revealing an interface forthe second mode of the first application 1305 includes displaying ananimation that translates the lock screen interface.

In some embodiments, the animation translates the lock screen interfacein a first direction to partially reveal the interface for the firstmode or the second mode of the first application 1305 and thentranslates the lock screen interface in a direction opposite the firstdirection to eliminate display of the partially revealed interface ofthe first application 1305.

In some embodiments, the processing unit 1306 is configured to: inresponse to a determination that the gesture starts on the firstapplication access indicia and is a third type of gesture, distinct fromthe first type of gesture and the second type of gesture, enable displayof one or more visual cues of the first type of gesture and the secondtype of gesture (e.g., with the display enabling unit 1314).

In some embodiments, the processing unit 1306 is configured to: inresponse to a determination that the gesture starts at a location on thetouch-sensitive display other than the first application access indicia,enable display of a passcode entry interface (e.g., with the displayenabling unit 1314), wherein in response to entry of a correct passcodein the passcode entry interface, the passcode entry interface ceases tobe displayed and the device enters an unlocked state with access to theplurality of applications 1304.

In some embodiments, the first type of gesture includes a contact movingin a first path on the touch-sensitive surface, and the second type ofgesture includes a contact moving in a second path distinct from thefirst path on the touch-sensitive surface.

In some embodiments, the first type of gesture includes a contact movingto and ending at a first region on the touch-sensitive surface, and thesecond type of gesture includes a contact moving to and ending at asecond region, distinct from the first region, on the touch-sensitivesurface.

In some embodiments, the first type of gesture includes a first numberof contacts, and the second type of gesture includes a second number ofcontacts different from the first number of contacts.

In some embodiments, the first application 1305 is a camera application,the first mode is a still image capture mode, and the second mode is avideo capture mode.

In some embodiments, the first application 1305 is a notificationsapplication, the first mode is an incoming messages notifications mode,and the second mode is an aggregate notifications mode.

In some embodiments, the first application 1305 is an email application,the first mode is an inbox mode, and the second mode is an emailcomposition mode.

In some embodiments, the first application 1305 is a phone application,the first mode is a keypad mode, and the second mode is a recent callslisting mode.

In some embodiments, the first application 1305 is a phone application,the first mode is a keypad mode, and the second mode is a voicemailmode.

In some embodiments, the processing unit 1306 is configured to: enabledisplay of an animation that changes the first application accessindicia from a first graphic that corresponds to the first mode to asecond graphic, distinct from the first graphic, that corresponds to thesecond mode (e.g., with the display enabling unit 1314).

In some other embodiments, an electronic device 1300 includes atouch-sensitive display unit 1302 configured to display, while thedevice is in a locked, passcode-protected state, a lock screeninterface, the lock screen interface including a first access indiciafor a first mode in a first application 1305 and a second accessindicia, distinct from the first access indicia, for a second mode inthe first application 1305, and receive gestures; a plurality ofapplications 1304, including a first application 1305; and a processingunit 1306 coupled to the touch-sensitive display unit 1302 and theplurality of applications 1304. In some embodiments, the processing unit1306 includes a detecting unit 1308, a ceasing unit 1310, a startingunit 1312, a display enabling unit 1314, a maintaining unit 1316, and arevealing unit 1318.

The processing unit 1306 is configured to: while the device is in alocked, passcode-protected state: detect a gesture on thetouch-sensitive display (e.g,, with the detecting unit 1308); inresponse to a determination that the gesture starts on the first accessindicia and is a first type of gesture, cease to display the lock screeninterface (e.g., with the ceasing unit 1310), start a restricted sessionfor the first application 1305 in a first mode of the first application1305 (e.g., with the starting unit 1312), enable display of an interfacefor the first application 1305 in the first mode, without displaying apasscode entry interface (e.g., with the display enabling unit 1314),and maintain the device in the locked, passcode-protected state forapplications 1304 in the device other than the first application 1305(e.g., with the maintaining unit 1316); and in response to adetermination that the gesture starts on the second access indicia andis a second type of gesture: cease to display the lock screen interface(e.g., with the ceasing unit 1310), start a restricted session for thefirst application 1305 in a second mode of the first application 1305,distinct from the first mode of the first application 1305 (e.g., withthe starting unit 1312), enable display of an interface for the firstapplication 1305 in the second mode, without displaying a passcode entryinterface (e.g., with the display enabling unit 1314), and maintain thedevice in the locked, passcode-protected state for applications 1304 inthe device other than the first application 1305 (e.g., with themaintaining unit 1316).

In some embodiments, the processing unit 1306 is configured to: inresponse to a determination that the gesture starts on the first accessindicia and is a type of gesture distinct from the first type ofgesture, partially reveal an interface for the first mode of the firstapplication 1305 (e.g., with the revealing unit 1318), and, in responseto a determination that the gesture starts on the second access indiciaand is a type of gesture distinct from the second type of gesture,partially reveal an interface for the second mode of the firstapplication 1305 (e.g., with the revealing unit 1318).

In some embodiments, the type of gesture distinct from the first type ofgesture is a tap gesture, and the type of gesture distinct from thesecond type of gesture is a tap gesture.

In some embodiments, partially revealing an interface for the first modeof the application includes displaying an animation of the lock screeninterface translating in a. first direction, and partially revealing aninterface for the second mode of the application includes displaying ananimation of the lock screen interface translating in a seconddirection, distinct from the first direction.

In some embodiments, the second direction is orthogonal to the firstdirection.

In some embodiments, the second type of gesture is distinct from thefirst type of gesture.

In some embodiments, the processing unit 1306 is configured to: inresponse to a determination that the gesture starts at a location on thetouch-sensitive display other than the first access indicia and thesecond access indicia, enable display of a passcode entry interface(e.g., with the display enabling unit 1314), wherein in response toentry of a correct passcode in the passcode entry interface, thepasscode entry interface ceases to be displayed and the device enters anunlocked state with access to the plurality of applications 1304.

In some embodiments, the first type of gesture includes a contact movingin a first path on the touch-sensitive surface, and the second type ofgesture includes a contact moving in a second path distinct from thefirst path on the touch-sensitive surface.

In some embodiments, the first type of gesture includes a contact movingto and ending at a first region on the touch-sensitive surface, and thesecond type of gesture includes a contact moving to and ending at asecond region, distinct from the first region, on the touch-sensitivesurface.

In some embodiments, the first type gesture includes a first number ofcontacts, and the second type of gesture includes a second number ofcontacts different from the first number of contacts.

In some embodiments, the first application 1305 is a camera application,the first mode is a still image capture mode, and the second mode is avideo capture mode.

In some embodiments, the first application 1305 is a notificationsapplication, the first mode is an incoming messages notifications mode,and the second mode is an aggregate notifications mode.

In some embodiments, the first application 1305 is an email application,the first mode is an inbox mode, and the second mode is an emailcomposition mode.

In some embodiments, the first application 1305 is a phone application,the first mode is a keypad mode. and the second mode is a recent callslisting mode.

In some embodiments, the first application 1305 is a phone application,the first mode is a keypad mode, and the second mode is a voicemailmode.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A and 3) are all included within the scope ofprotection of the invention.

The operations described above with reference to FIGS. 6A-6B, 7-9,10A-10C, 11A-11C may be implemented by components depicted in FIGS.1A-1B. For example, detection operation 608, ceasing operation 620,starting operation 622, displaying operation 624, and maintainingoperation 626 may be implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub-event, such as selection of anobject on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 may utilize or call data updater 176 or object updater 177to update the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. (canceled)
 2. An electronic device, comprising: a touch-sensitivedisplay; one or more processors; memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: while the device is in a lockedstate: displaying a first locked device interface page on thetouch-sensitive display; detecting a gesture on the touch-sensitivedisplay; in accordance with a determination that the gesture includesmovement in a first direction: ceasing to display the first lockeddevice interface page; displaying an interface for a camera applicationin a restricted session; and maintaining the device in the locked statefor applications in the device other than the camera application; and inaccordance with a determination that the gesture includes movement in asecond direction opposite to the first direction: displaying a secondlocked device interface page different from the first locked deviceinterface page.
 3. The electronic device of claim 2, wherein the secondlocked device interface page includes media playback controls.
 4. Theelectronic device of claim 2, wherein the gesture is a single fingerslide gesture.
 5. The electronic device of claim 2, wherein the one ormore programs further include instructions for: in accordance with thedetermination that the gesture includes movement in the first direction:initializing one or more hardware components in a camera that iscontrolled by the camera application.
 6. The electronic device of claim2, wherein: while the camera application is in the restricted session:the camera application is enabled to present one or more imagesgenerated by the camera application while in the restricted session; andthe camera application is disabled from presenting any images in thecamera application that were not generated while in the restrictedsession.
 7. The electronic device of claim 2, wherein the one or moreprograms further include instructions for: while the device is in thelocked state: preventing the device from performing a predefined set ofactions in response to detecting contact with the touch-sensitivedisplay that does not correspond to the gesture.
 8. The electronicdevice of claim 2, wherein displaying the interface for the cameraapplication includes: displaying an animation translating the firstlocked device interface page off the display while revealing theinterface for the camera application in accordance with the firstdirection of movement.
 9. A non-transitory computer-readable storagemedium storing one or more programs configured to be executed by one ormore processors of an electronic device with a touch-sensitive display,the one or more programs including instructions for: while the device isin a locked state: displaying a first locked device interface page onthe touch-sensitive display; detecting a gesture on the touch-sensitivedisplay; in accordance with a determination that the gesture includesmovement in a first direction: ceasing to display the first lockeddevice interface page; displaying an interface for a camera applicationin a restricted session; and maintaining the device in the locked statefor applications in the device other than the camera application; and inaccordance with a determination that the gesture includes movement in asecond direction opposite to the first direction: displaying a secondlocked device interface page different from the first locked deviceinterface page.
 10. The non-transitory computer-readable storage mediumof claim 9, wherein the second locked device interface page includesmedia playback controls.
 11. The non-transitory computer-readablestorage medium of claim 9, wherein the gesture is a single finger slidegesture.
 12. The non-transitory computer-readable storage medium ofclaim 9, wherein the one or more programs further include instructionsfor: in accordance with the determination that the gesture includesmovement in the first direction: initializing one or more hardwarecomponents in a camera that is controlled by the camera application. 13.The non-transitory computer-readable storage medium of claim 9, wherein:while the camera application is in the restricted session: the cameraapplication is enabled to present one or more images generated by thecamera application while in the restricted session; and the cameraapplication is disabled from presenting any images in the cameraapplication that were not generated while in the restricted session. 14.The non-transitory computer-readable storage medium of claim 9, whereinthe one or more programs further include instructions for: while thedevice is in the locked state: preventing the device from performing apredefined set of actions in response to detecting contact with thetouch-sensitive display that does not correspond to the gesture.
 15. Thenon-transitory computer-readable storage medium of claim 9, whereindisplaying the interface for the camera application includes: displayingan animation translating the first locked device interface page off thedisplay while revealing the interface for the camera application inaccordance with the first direction of movement.
 16. A method,comprising: at an electronic device with a touch-sensitive display:while the device is in a locked state: displaying a first locked deviceinterface page on the touch-sensitive display; detecting a gesture onthe touch-sensitive display; in accordance with a determination that thegesture includes movement in a first direction: ceasing to display thefirst locked device interface page; displaying an interface for a cameraapplication in a restricted session; and maintaining the device in thelocked state for applications in the device other than the cameraapplication; and in accordance with a determination that the gestureincludes movement in a second direction opposite to the first direction:displaying a second locked device interface page different from thefirst locked device interface page.
 17. The method of claim 16, whereinthe second locked device interface page includes media playbackcontrols.
 18. The method of claim 16, wherein the gesture is a singlefinger slide gesture.
 19. The method of claim 16, further comprising: inaccordance with the determination that the gesture includes movement inthe first direction: initializing one or more hardware components in acamera that is controlled by the camera application.
 20. The method ofclaim 16, wherein: while the camera application is in the restrictedsession: the camera application is enabled to present one or more imagesgenerated by the camera application while in the restricted session; andthe camera application is disabled from presenting any images in thecamera application that were not generated while in the restrictedsession.
 21. The method of claim 16, further comprising: while thedevice is in the locked state: preventing the device from performing apredefined set of actions in response to detecting contact with thetouch-sensitive display that does not correspond to the gesture.
 22. Themethod of claim 16, wherein displaying the interface for the cameraapplication includes: displaying an animation translating the firstlocked device interface page off the display while revealing theinterface for the camera application in accordance with the firstdirection of movement.